<?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 Re: Custom PostgreSQL plugin for collecting metrics from Openshift Pods in Extensions</title>
    <link>https://community.dynatrace.com/t5/Extensions/Custom-PostgreSQL-plugin-for-collecting-metrics-from-Openshift/m-p/125221#M1247</link>
    <description>&lt;P&gt;I seem to have missed that plugins are not supported when running dynatrace from containers in pods, even though it is clearly stated in the documentation:&lt;BR /&gt;&lt;A rel="noopener noreferrer" href="https://www.dynatrace.com/support/help/technology-support/supported-technologies-and-versions/#plugins" target="_blank"&gt;https://www.dynatrace.com/support/help/technology-support/supported-technologies-and-versions/#plugins&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;So to actually monitor postgreSQL OpenShift services, some workaround must be configured.&lt;BR /&gt;&lt;BR /&gt;(Contemplating an ugly hack with HAProxy tcp lb with configured nodeports)&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 14 Nov 2019 14:30:10 GMT</pubDate>
    <dc:creator>rasmus_edgar_fi</dc:creator>
    <dc:date>2019-11-14T14:30:10Z</dc:date>
    <item>
      <title>Custom PostgreSQL plugin for collecting metrics from Openshift Pods</title>
      <link>https://community.dynatrace.com/t5/Extensions/Custom-PostgreSQL-plugin-for-collecting-metrics-from-Openshift/m-p/125220#M1246</link>
      <description>&lt;P&gt;I have customized the original PostgreSQL plugin and added a service_name field in order to connect to the OpenShift PostgreSQL services running in pods.&lt;BR /&gt;&lt;BR /&gt;The custom plugin installs in the tenant without issue and I can enter and save login credentials.&lt;BR /&gt;&lt;BR /&gt;No metrics are collected.&lt;BR /&gt;&lt;BR /&gt;Am I supposed to deploy the custom plugin manually on the OpenShift nodes in /opt/dynatrace/oneagent/plugin_deployment or somewhere else?&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 13 Nov 2019 13:30:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/Custom-PostgreSQL-plugin-for-collecting-metrics-from-Openshift/m-p/125220#M1246</guid>
      <dc:creator>rasmus_edgar_fi</dc:creator>
      <dc:date>2019-11-13T13:30:21Z</dc:date>
    </item>
    <item>
      <title>Re: Custom PostgreSQL plugin for collecting metrics from Openshift Pods</title>
      <link>https://community.dynatrace.com/t5/Extensions/Custom-PostgreSQL-plugin-for-collecting-metrics-from-Openshift/m-p/125221#M1247</link>
      <description>&lt;P&gt;I seem to have missed that plugins are not supported when running dynatrace from containers in pods, even though it is clearly stated in the documentation:&lt;BR /&gt;&lt;A rel="noopener noreferrer" href="https://www.dynatrace.com/support/help/technology-support/supported-technologies-and-versions/#plugins" target="_blank"&gt;https://www.dynatrace.com/support/help/technology-support/supported-technologies-and-versions/#plugins&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;So to actually monitor postgreSQL OpenShift services, some workaround must be configured.&lt;BR /&gt;&lt;BR /&gt;(Contemplating an ugly hack with HAProxy tcp lb with configured nodeports)&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Nov 2019 14:30:10 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/Custom-PostgreSQL-plugin-for-collecting-metrics-from-Openshift/m-p/125221#M1247</guid>
      <dc:creator>rasmus_edgar_fi</dc:creator>
      <dc:date>2019-11-14T14:30:10Z</dc:date>
    </item>
  </channel>
</rss>

