{"id":6423,"date":"2015-12-06T17:16:14","date_gmt":"2015-12-06T16:16:14","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/"},"modified":"2015-12-06T17:16:14","modified_gmt":"2015-12-06T16:16:14","slug":"sql-monitoring-in-postgresql-2-pg_stat_statements","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/","title":{"rendered":"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements"},"content":{"rendered":"<p>The <a href=\"http:\/\/dbi-services.com\/blog\/sql-monitoring-in-postgresql-1-the-logging-system\/\" target=\"_blank\" rel=\"noopener\">last post<\/a> looked into how you can monitor queries using the logging system. This post will introduce <a href=\"http:\/\/www.postgresql.org\/docs\/current\/static\/pgstatstatements.html\" target=\"_blank\" rel=\"noopener\">pg_stat_statements<\/a>. <\/p>\n<p>pg_stat_statements is a module that needs to be loaded and is not available in the default configuration. Loading it is quite easy. Create the extension as usual:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres@oel7:\/home\/postgres\/ [PG6] sqh\nNull display is \"NULL\".\nTiming is on.\npsql (9.5alpha2)\nType \"help\" for help.\n\n(postgres@[local]:4448) [postgres] &gt; create extension pg_stat_statements;\nCREATE EXTENSION\nTime: 281.765 ms\n(postgres@[local]:4448) [postgres] &gt; dx\n                                     List of installed extensions\n        Name        | Version |   Schema   |                        Description                        \n--------------------+---------+------------+-----------------------------------------------------------\n btree_gist         | 1.1     | public     | support for indexing common datatypes in GiST\n pg_stat_statements | 1.3     | public     | track execution statistics of all SQL statements executed\n plpgsql            | 1.0     | pg_catalog | PL\/pgSQL procedural language\n postgres_fdw       | 1.0     | public     | foreign-data wrapper for remote PostgreSQL servers\n(4 rows)\n<\/pre>\n<p>After the extension is available we need to adjust the <a href=\"http:\/\/www.postgresql.org\/docs\/current\/static\/runtime-config-client.html#GUC-SHARED-PRELOAD-LIBRARIES\" target=\"_blank\" rel=\"noopener\">shared_preload_libraries<\/a> parameter:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\n(postgres@[local]:4448) [postgres] &gt; show shared_preload_libraries;\n shared_preload_libraries \n--------------------------\n \n(1 row)\n\n(postgres@[local]:4448) [postgres] &gt; alter system set shared_preload_libraries='pg_stat_statements';\nALTER SYSTEM\nTime: 55.005 ms\n\n(postgres@[local]:4448) [postgres] &gt; select name,pending_restart \n                                       from pg_settings \n                                      where name in ('shared_preload_libraries');\n           name           | pending_restart \n--------------------------+-----------------\n shared_preload_libraries | f\n(1 row)\n\nTime: 1.517 ms\n(postgres@[local]:4448) [postgres] &gt; select pg_reload_conf();\n pg_reload_conf \n----------------\n t\n(1 row)\n<\/pre>\n<p>Basically pg_stat_statements can be used from now own. But there are some parameters to look at if you want to fine tune. Check the <a href=\"http:\/\/www.postgresql.org\/docs\/current\/static\/pgstatstatements.html\" target=\"_blank\" rel=\"noopener\">documentation<\/a> for the description.<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\n(postgres@[local]:4448) [postgres] &gt; show pg_stat_statements.max;\n-[ RECORD 1 ]----------+-----\npg_stat_statements.max | 5000\n\nTime: 0.230 ms\n(postgres@[local]:4448) [postgres] &gt; show pg_stat_statements.track;\n-[ RECORD 1 ]------------+----\npg_stat_statements.track | top\n\nTime: 0.211 ms\n(postgres@[local]:4448) [postgres] &gt; show pg_stat_statements.track_utility;\n-[ RECORD 1 ]--------------------+---\npg_stat_statements.track_utility | on\n\nTime: 0.215 ms\n(postgres@[local]:4448) [postgres] &gt; show pg_stat_statements.save;\n-[ RECORD 1 ]-----------+---\npg_stat_statements.save | on\n\nTime: 0.212 ms\n<\/pre>\n<p>When we installed the extension a view was created with the <a href=\"http:\/\/www.postgresql.org\/docs\/current\/static\/pgstatstatements.html#PGSTATSTATEMENTS-COLUMNS\" target=\"_blank\" rel=\"noopener\">following columns<\/a>:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\n(postgres@[local]:4448) [postgres] &gt; d pg_stat_statements\n          View \"public.pg_stat_statements\"\n       Column        |       Type       | Modifiers \n---------------------+------------------+-----------\n userid              | oid              | \n dbid                | oid              | \n queryid             | bigint           | \n query               | text             | \n calls               | bigint           | \n total_time          | double precision | \n min_time            | double precision | \n max_time            | double precision | \n mean_time           | double precision | \n stddev_time         | double precision | \n rows                | bigint           | \n shared_blks_hit     | bigint           | \n shared_blks_read    | bigint           | \n shared_blks_dirtied | bigint           | \n shared_blks_written | bigint           | \n local_blks_hit      | bigint           | \n local_blks_read     | bigint           | \n local_blks_dirtied  | bigint           | \n local_blks_written  | bigint           | \n temp_blks_read      | bigint           | \n temp_blks_written   | bigint           | \n blk_read_time       | double precision | \n blk_write_time      | double precision | \n<\/pre>\n<p>We can now query the view for information we are interested in, e.g.:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\n(postgres@[local]:4448) [postgres] &gt; x\nExpanded display is on.\n(postgres@[local]:4448) [postgres] &gt; select userid,query,calls,total_time from pg_stat_statements;\n-[ RECORD 1 ]\nuserid     | 10\nquery      | alter system set logging_collector=on;\ncalls      | 1\ntotal_time | 30.13\n-[ RECORD 2 ]\nuserid     | 10\nquery      | create extension pg_stat_statements;\ncalls      | 2\ntotal_time | 250.54\n-[ RECORD 3 ]\nuserid     | 10\nquery      | select name,pending_restart from pg_settings where name in (?,?,?,?,?);\ncalls      | 1\ntotal_time | 0.627\n-[ RECORD 4 ]\nuserid     | 10\nquery      | show log_rotation_size;\ncalls      | 1\ntotal_time | 0.006\n<\/pre>\n<p>Additionally we can call a function which is named exactly the same as the view:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\n(postgres@[local]:4448) [postgres] &gt; select * from pg_stat_statements(true);\n-[ RECORD 1 ]\nuserid              | 10\ndbid                | 13295\nqueryid             | 780340104\nquery               | alter system set logging_collector=on;\ncalls               | 1\ntotal_time          | 30.13\nmin_time            | 30.13\nmax_time            | 30.13\nmean_time           | 30.13\nstddev_time         | 0\nrows                | 0\nshared_blks_hit     | 0\nshared_blks_read    | 0\nshared_blks_dirtied | 0\nshared_blks_written | 0\nlocal_blks_hit      | 0\nlocal_blks_read     | 0\nlocal_blks_dirtied  | 0\nlocal_blks_written  | 0\ntemp_blks_read      | 0\ntemp_blks_written   | 0\nblk_read_time       | 0\nblk_write_time      | 0\n-[ RECORD 2 ]\nuserid              | 10\ndbid                | 13295\nqueryid             | 1392856018\nquery               | create extension pg_stat_statements;\ncalls               | 2\ntotal_time          | 250.54\nmin_time            | 1.489\nmax_time            | 249.051\nmean_time           | 125.27\nstddev_time         | 123.781\nrows                | 0\nshared_blks_hit     | 1150\nshared_blks_read    | 90\nTime: 0.742 ms\n<\/pre>\n<p>On top of either the view or the function we can now start to troubleshoot issues with the queries the server executes. Hope this helps.<\/p>\n<p>In the next post I&#8217;ll introduce pg_activity.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The last post looked into how you can monitor queries using the logging system. This post will introduce pg_stat_statements. pg_stat_statements is a module that needs to be loaded and is not available in the default configuration. Loading it is quite easy. Create the extension as usual: postgres@oel7:\/home\/postgres\/ [PG6] sqh Null display is &#8220;NULL&#8221;. Timing is [&hellip;]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[143,77,98],"type_dbi":[],"class_list":["post-6423","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-monitoring","tag-postgresql","tag-sql"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements\" \/>\n<meta property=\"og:description\" content=\"The last post looked into how you can monitor queries using the logging system. This post will introduce pg_stat_statements. pg_stat_statements is a module that needs to be loaded and is not available in the default configuration. Loading it is quite easy. Create the extension as usual: postgres@oel7:\/home\/postgres\/ [PG6] sqh Null display is &quot;NULL&quot;. Timing is [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2015-12-06T16:16:14+00:00\" \/>\n<meta name=\"author\" content=\"Daniel Westermann\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@westermanndanie\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Westermann\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements\",\"datePublished\":\"2015-12-06T16:16:14+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/\"},\"wordCount\":177,\"commentCount\":0,\"keywords\":[\"Monitoring\",\"PostgreSQL\",\"SQL\"],\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/\",\"name\":\"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2015-12-06T16:16:14+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\",\"name\":\"Daniel Westermann\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"caption\":\"Daniel Westermann\"},\"description\":\"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &amp;\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.\",\"sameAs\":[\"https:\/\/x.com\/westermanndanie\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/","og_locale":"en_US","og_type":"article","og_title":"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements","og_description":"The last post looked into how you can monitor queries using the logging system. This post will introduce pg_stat_statements. pg_stat_statements is a module that needs to be loaded and is not available in the default configuration. Loading it is quite easy. Create the extension as usual: postgres@oel7:\/home\/postgres\/ [PG6] sqh Null display is \"NULL\". Timing is [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/","og_site_name":"dbi Blog","article_published_time":"2015-12-06T16:16:14+00:00","author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements","datePublished":"2015-12-06T16:16:14+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/"},"wordCount":177,"commentCount":0,"keywords":["Monitoring","PostgreSQL","SQL"],"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/","url":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/","name":"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2015-12-06T16:16:14+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/sql-monitoring-in-postgresql-2-pg_stat_statements\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL Monitoring in PostgreSQL (2) \u2013 pg_stat_statements"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66","name":"Daniel Westermann","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","caption":"Daniel Westermann"},"description":"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &amp;\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.","sameAs":["https:\/\/x.com\/westermanndanie"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/6423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=6423"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/6423\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=6423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=6423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=6423"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=6423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}