<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic GKE PostgreSQL database merging in Cloud platforms</title>
    <link>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/203728#M1067</link>
    <description>&lt;P&gt;Hi, in one of our monitored GKE clusters we have several PostgreSQL databases. The problem is that for each worker node, a new instance of PostgreSQL database is detected (see image below). That's formally correct but we'd like to be able to merge those databases into a single one to simplify analysis and troubleshooting.&lt;/P&gt;
&lt;P&gt;Any hint for this?&lt;/P&gt;
&lt;P&gt;Thanks&lt;BR /&gt;PF&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="paolo_fumanelli_1-1675174209480.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/9733iCD0E30FDC250ADD7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="paolo_fumanelli_1-1675174209480.png" alt="paolo_fumanelli_1-1675174209480.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jun 2023 08:47:59 GMT</pubDate>
    <dc:creator>paolo_fumanelli</dc:creator>
    <dc:date>2023-06-14T08:47:59Z</dc:date>
    <item>
      <title>GKE PostgreSQL database merging</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/203728#M1067</link>
      <description>&lt;P&gt;Hi, in one of our monitored GKE clusters we have several PostgreSQL databases. The problem is that for each worker node, a new instance of PostgreSQL database is detected (see image below). That's formally correct but we'd like to be able to merge those databases into a single one to simplify analysis and troubleshooting.&lt;/P&gt;
&lt;P&gt;Any hint for this?&lt;/P&gt;
&lt;P&gt;Thanks&lt;BR /&gt;PF&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="paolo_fumanelli_1-1675174209480.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/9733iCD0E30FDC250ADD7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="paolo_fumanelli_1-1675174209480.png" alt="paolo_fumanelli_1-1675174209480.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2023 08:47:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/203728#M1067</guid>
      <dc:creator>paolo_fumanelli</dc:creator>
      <dc:date>2023-06-14T08:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: GKE PostgreSQL database merging</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/207700#M1119</link>
      <description>&lt;P&gt;hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/19328"&gt;@paolo_fumanelli&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I encounter the same issue as you on GKE environment with PostgreSQL.&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Same issue here. We are using SQL-Proxies (client com.google.cloud.sql.postgres.SocketFactory) on all kubernetes Nodes to connect to our Database.&lt;/P&gt;&lt;P&gt;Dynatrace perceives a databases per node&amp;nbsp;:&lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AurelienGravier_1-1679502893789.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/10623i50098215E1DA3E37/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AurelienGravier_1-1679502893789.png" alt="AurelienGravier_1-1679502893789.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Properties are the same for earch database service :&lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AurelienGravier_2-1679502966869.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/10624i251DEF3C689FE7FF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AurelienGravier_2-1679502966869.png" alt="AurelienGravier_2-1679502966869.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The connection string used is :&lt;/P&gt;&lt;P&gt;spring:&lt;/P&gt;&lt;P&gt;datasource:&lt;BR /&gt;url: jdbc:postgresql:///${ClientName.sql.database-name}&lt;BR /&gt;hikari:&lt;BR /&gt;minimum-idle: 1&lt;BR /&gt;maximum-pool-size: 20&lt;BR /&gt;data-source-properties:&lt;BR /&gt;sslmode: disable&lt;BR /&gt;socketFactory: com.google.cloud.sql.postgres.SocketFactory&lt;BR /&gt;cloudSqlInstance: ${ClientName.sql.instance-connection-name}&lt;BR /&gt;enableIamAuth: true&lt;BR /&gt;user: ${ClientName.sql.username}&lt;/P&gt;&lt;P&gt;schema: db_amx&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you find a workaround ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 22 Mar 2023 16:40:56 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/207700#M1119</guid>
      <dc:creator>AurelienGravier</dc:creator>
      <dc:date>2023-03-22T16:40:56Z</dc:date>
    </item>
    <item>
      <title>Re: GKE PostgreSQL database merging</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/207741#M1122</link>
      <description>&lt;P&gt;Hello Aurelien, unfortunately I didn't. Our main contact in Dynatrace told us that some news regarding database service should come later in the next quarters but no precise news about it.ù&lt;/P&gt;&lt;P&gt;bye&lt;BR /&gt;Paolo&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 08:07:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/207741#M1122</guid>
      <dc:creator>paolo_fumanelli</dc:creator>
      <dc:date>2023-03-23T08:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: GKE PostgreSQL database merging</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/211483#M1153</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/19328"&gt;@paolo_fumanelli&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;I created the following RFE, I suggest voting and adding a comment from your side :&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.dynatrace.com/t5/Product-ideas/Make-Dynatrace-compatible-with-Google-Cloud-SQL-IAM-database/idi-p/211279" target="_blank"&gt;https://community.dynatrace.com/t5/Product-ideas/Make-Dynatrace-compatible-with-Google-Cloud-SQL-IAM-database/idi-p/211279&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;</description>
      <pubDate>Fri, 05 May 2023 07:47:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/211483#M1153</guid>
      <dc:creator>AurelienGravier</dc:creator>
      <dc:date>2023-05-05T07:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: GKE PostgreSQL database merging</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/211486#M1154</link>
      <description>&lt;P&gt;Great, thank you&lt;/P&gt;</description>
      <pubDate>Fri, 05 May 2023 08:04:20 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/GKE-PostgreSQL-database-merging/m-p/211486#M1154</guid>
      <dc:creator>paolo_fumanelli</dc:creator>
      <dc:date>2023-05-05T08:04:20Z</dc:date>
    </item>
  </channel>
</rss>

