<?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 Monitoring Cloud PKI API endpoints in Synthetic Monitoring</title>
    <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/Monitoring-Cloud-PKI-API-endpoints/m-p/190963#M1418</link>
    <description>&lt;P&gt;For monitoring various APIs with the Synthetics, we need to have Accounts/Certificates to configure for access. As far as the Application/Service Accounts we can use within Dynatrace to configure monitoring like this, &amp;nbsp;we have a few questions:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;With Application API's we can utilize AD or LDAP Service Accounts, but with Secret Server API it would require a Secret Server Application Account. Will we would need to create one specific to the Dynatrace solution, correct?&lt;/LI&gt;
&lt;LI&gt;As for the CA APIs, they will require a certificate to be generated to provide access. We want to see if there would be a way we could automate the renewal/installation of the certificates generated for this monitoring?&lt;/LI&gt;
&lt;LI&gt;But, we would need to get more information on how Dynatrace would utilize the certificate and how it is installed. If we can automate the renewal or not?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Please help us out...&lt;/P&gt;</description>
    <pubDate>Thu, 21 Jul 2022 14:37:41 GMT</pubDate>
    <dc:creator>dnpmoris</dc:creator>
    <dc:date>2022-07-21T14:37:41Z</dc:date>
    <item>
      <title>Monitoring Cloud PKI API endpoints</title>
      <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/Monitoring-Cloud-PKI-API-endpoints/m-p/190963#M1418</link>
      <description>&lt;P&gt;For monitoring various APIs with the Synthetics, we need to have Accounts/Certificates to configure for access. As far as the Application/Service Accounts we can use within Dynatrace to configure monitoring like this, &amp;nbsp;we have a few questions:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;With Application API's we can utilize AD or LDAP Service Accounts, but with Secret Server API it would require a Secret Server Application Account. Will we would need to create one specific to the Dynatrace solution, correct?&lt;/LI&gt;
&lt;LI&gt;As for the CA APIs, they will require a certificate to be generated to provide access. We want to see if there would be a way we could automate the renewal/installation of the certificates generated for this monitoring?&lt;/LI&gt;
&lt;LI&gt;But, we would need to get more information on how Dynatrace would utilize the certificate and how it is installed. If we can automate the renewal or not?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Please help us out...&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2022 14:37:41 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Synthetic-Monitoring/Monitoring-Cloud-PKI-API-endpoints/m-p/190963#M1418</guid>
      <dc:creator>dnpmoris</dc:creator>
      <dc:date>2022-07-21T14:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring Cloud PKI API endpoints</title>
      <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/Monitoring-Cloud-PKI-API-endpoints/m-p/191140#M1419</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.dynatrace.com/platform/cloud-automation/" target="_self"&gt;Dynatrace cloud automation&lt;/A&gt; with other third party tools like Monaco and others can be used to define the required SLO and automate the deployment.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2022 07:26:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Synthetic-Monitoring/Monitoring-Cloud-PKI-API-endpoints/m-p/191140#M1419</guid>
      <dc:creator>techean</dc:creator>
      <dc:date>2022-07-22T07:26:02Z</dc:date>
    </item>
  </channel>
</rss>

