<?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 Tip: How Certificate Check Intervals Influence SSL/TLS Problem Detection &amp;amp; Resolution in Dynatrace in Dynatrace tips</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-tips/Tip-How-Certificate-Check-Intervals-Influence-SSL-TLS-Problem/m-p/293712#M1871</link>
    <description>&lt;DIV&gt;
&lt;P&gt;Understanding how Dynatrace handles SSL/TLS certificate checks is essential for accurately interpreting problem lifecycles, especially when issues seem to remain open longer than expected or reappear after process restarts. Below is a clear explanation that helps clarify why this happens.&lt;/P&gt;
&lt;H2&gt;&lt;span class="lia-unicode-emoji" title=":pushpin:"&gt;📌&lt;/span&gt;What the Certificate Check Interval Actually Controls&lt;/H2&gt;
&lt;P&gt;The &lt;STRONG&gt;certificate check interval&lt;/STRONG&gt; determines how often Dynatrace performs certificate discovery and metadata updates &lt;EM&gt;and&lt;/EM&gt; how certificate‑related problems are opened and closed.&lt;/P&gt;
&lt;P&gt;When Dynatrace identifies an expired or soon‑to‑expire certificate, the problem stays open &lt;STRONG&gt;until the next scheduled check&lt;/STRONG&gt; confirms the issue is resolved. Even if the certificate is renewed immediately, &lt;STRONG&gt;Dynatrace will not close the problem instantly&lt;/STRONG&gt;—it waits for the next interval to validate the updated certificate.&lt;/P&gt;
&lt;H3&gt;Example&lt;/H3&gt;
&lt;P&gt;If the check interval is &lt;STRONG&gt;24 hours&lt;/STRONG&gt;, any certificate problem will remain open for &lt;STRONG&gt;at least 24 hours&lt;/STRONG&gt;.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Long intervals → problems stay open longer&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Short intervals → quicker validation and closure&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2&gt;&lt;span class="lia-unicode-emoji" title=":counterclockwise_arrows_button:"&gt;🔄&lt;/span&gt;How Process Restarts Affect Certificate Problems&lt;/H2&gt;
&lt;P&gt;Dynatrace ties certificate problems to the &lt;STRONG&gt;specific process instance&lt;/STRONG&gt; (process ID) from which the certificate was discovered.&lt;BR /&gt;This means if the monitored process is:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Restarted&lt;/LI&gt;
&lt;LI&gt;Terminated&lt;/LI&gt;
&lt;LI&gt;Crashed&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;…before the next certificate check runs, Dynatrace will &lt;STRONG&gt;automatically close the existing problem&lt;/STRONG&gt;, because the original process no longer exists in the environment.&lt;/P&gt;
&lt;H3&gt;What Happens Next?&lt;/H3&gt;
&lt;P&gt;During the next certificate check interval:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Dynatrace re‑evaluates the certificate&lt;/LI&gt;
&lt;LI&gt;If the issue still exists, &lt;STRONG&gt;a new problem is created&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;This is common when certificates are discovered from &lt;STRONG&gt;short‑lived or frequently restarting processes&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Even though the &lt;STRONG&gt;custom device&lt;/STRONG&gt; linked to the certificate stays the same, each process restart creates a new process ID. Dynatrace treats this as a new monitored entity, resulting in:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Old problem closed with the old process&lt;/LI&gt;
&lt;LI&gt;New problem opened when the certificate issue is detected again&lt;/LI&gt;
&lt;/OL&gt;
&lt;H2&gt;&lt;span class="lia-unicode-emoji" title=":memo:"&gt;📝&lt;/span&gt;Summary&lt;/H2&gt;
&lt;P&gt;Dynatrace’s problem lifecycle for certificate issues depends on two key factors:&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;1. Certificate Check Interval&lt;/STRONG&gt;&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;Determines how often Dynatrace validates certificates&lt;/LI&gt;
&lt;LI&gt;Controls how long certificate problems remain open&lt;/LI&gt;
&lt;LI&gt;Influences how quickly problems close after renewal&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;&lt;STRONG&gt;2. Process Instance Status&lt;/STRONG&gt;&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;Certificate problems are tied to the specific process ID&lt;/LI&gt;
&lt;LI&gt;Restarts or crashes automatically close existing problems&lt;/LI&gt;
&lt;LI&gt;New problems may appear during the next check if the issue persists&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV&gt;#SSLCertificates #ProblemDetection #ProcessMonitoring&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Happy Dynatracing!!!&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Wed, 28 Jan 2026 08:13:55 GMT</pubDate>
    <dc:creator>AravindhanV</dc:creator>
    <dc:date>2026-01-28T08:13:55Z</dc:date>
    <item>
      <title>Tip: How Certificate Check Intervals Influence SSL/TLS Problem Detection &amp; Resolution in Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-tips/Tip-How-Certificate-Check-Intervals-Influence-SSL-TLS-Problem/m-p/293712#M1871</link>
      <description>&lt;DIV&gt;
&lt;P&gt;Understanding how Dynatrace handles SSL/TLS certificate checks is essential for accurately interpreting problem lifecycles, especially when issues seem to remain open longer than expected or reappear after process restarts. Below is a clear explanation that helps clarify why this happens.&lt;/P&gt;
&lt;H2&gt;&lt;span class="lia-unicode-emoji" title=":pushpin:"&gt;📌&lt;/span&gt;What the Certificate Check Interval Actually Controls&lt;/H2&gt;
&lt;P&gt;The &lt;STRONG&gt;certificate check interval&lt;/STRONG&gt; determines how often Dynatrace performs certificate discovery and metadata updates &lt;EM&gt;and&lt;/EM&gt; how certificate‑related problems are opened and closed.&lt;/P&gt;
&lt;P&gt;When Dynatrace identifies an expired or soon‑to‑expire certificate, the problem stays open &lt;STRONG&gt;until the next scheduled check&lt;/STRONG&gt; confirms the issue is resolved. Even if the certificate is renewed immediately, &lt;STRONG&gt;Dynatrace will not close the problem instantly&lt;/STRONG&gt;—it waits for the next interval to validate the updated certificate.&lt;/P&gt;
&lt;H3&gt;Example&lt;/H3&gt;
&lt;P&gt;If the check interval is &lt;STRONG&gt;24 hours&lt;/STRONG&gt;, any certificate problem will remain open for &lt;STRONG&gt;at least 24 hours&lt;/STRONG&gt;.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Long intervals → problems stay open longer&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Short intervals → quicker validation and closure&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2&gt;&lt;span class="lia-unicode-emoji" title=":counterclockwise_arrows_button:"&gt;🔄&lt;/span&gt;How Process Restarts Affect Certificate Problems&lt;/H2&gt;
&lt;P&gt;Dynatrace ties certificate problems to the &lt;STRONG&gt;specific process instance&lt;/STRONG&gt; (process ID) from which the certificate was discovered.&lt;BR /&gt;This means if the monitored process is:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Restarted&lt;/LI&gt;
&lt;LI&gt;Terminated&lt;/LI&gt;
&lt;LI&gt;Crashed&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;…before the next certificate check runs, Dynatrace will &lt;STRONG&gt;automatically close the existing problem&lt;/STRONG&gt;, because the original process no longer exists in the environment.&lt;/P&gt;
&lt;H3&gt;What Happens Next?&lt;/H3&gt;
&lt;P&gt;During the next certificate check interval:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Dynatrace re‑evaluates the certificate&lt;/LI&gt;
&lt;LI&gt;If the issue still exists, &lt;STRONG&gt;a new problem is created&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;This is common when certificates are discovered from &lt;STRONG&gt;short‑lived or frequently restarting processes&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Even though the &lt;STRONG&gt;custom device&lt;/STRONG&gt; linked to the certificate stays the same, each process restart creates a new process ID. Dynatrace treats this as a new monitored entity, resulting in:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Old problem closed with the old process&lt;/LI&gt;
&lt;LI&gt;New problem opened when the certificate issue is detected again&lt;/LI&gt;
&lt;/OL&gt;
&lt;H2&gt;&lt;span class="lia-unicode-emoji" title=":memo:"&gt;📝&lt;/span&gt;Summary&lt;/H2&gt;
&lt;P&gt;Dynatrace’s problem lifecycle for certificate issues depends on two key factors:&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;1. Certificate Check Interval&lt;/STRONG&gt;&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;Determines how often Dynatrace validates certificates&lt;/LI&gt;
&lt;LI&gt;Controls how long certificate problems remain open&lt;/LI&gt;
&lt;LI&gt;Influences how quickly problems close after renewal&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;&lt;STRONG&gt;2. Process Instance Status&lt;/STRONG&gt;&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;Certificate problems are tied to the specific process ID&lt;/LI&gt;
&lt;LI&gt;Restarts or crashes automatically close existing problems&lt;/LI&gt;
&lt;LI&gt;New problems may appear during the next check if the issue persists&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV&gt;#SSLCertificates #ProblemDetection #ProcessMonitoring&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Happy Dynatracing!!!&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 28 Jan 2026 08:13:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-tips/Tip-How-Certificate-Check-Intervals-Influence-SSL-TLS-Problem/m-p/293712#M1871</guid>
      <dc:creator>AravindhanV</dc:creator>
      <dc:date>2026-01-28T08:13:55Z</dc:date>
    </item>
  </channel>
</rss>

