Dynatrace tips
Tips and workarounds from Dynatrace users for Dynatrace users.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Tip: How Certificate Check Intervals Influence SSL/TLS Problem Detection & Resolution in Dynatrace

AravindhanV
Advisor

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.

📌What the Certificate Check Interval Actually Controls

The certificate check interval determines how often Dynatrace performs certificate discovery and metadata updates and how certificate‑related problems are opened and closed.

When Dynatrace identifies an expired or soon‑to‑expire certificate, the problem stays open until the next scheduled check confirms the issue is resolved. Even if the certificate is renewed immediately, Dynatrace will not close the problem instantly—it waits for the next interval to validate the updated certificate.

Example

If the check interval is 24 hours, any certificate problem will remain open for at least 24 hours.

  • Long intervals → problems stay open longer
  • Short intervals → quicker validation and closure

🔄How Process Restarts Affect Certificate Problems

Dynatrace ties certificate problems to the specific process instance (process ID) from which the certificate was discovered.
This means if the monitored process is:

  • Restarted
  • Terminated
  • Crashed

…before the next certificate check runs, Dynatrace will automatically close the existing problem, because the original process no longer exists in the environment.

What Happens Next?

During the next certificate check interval:

  • Dynatrace re‑evaluates the certificate
  • If the issue still exists, a new problem is created
  • This is common when certificates are discovered from short‑lived or frequently restarting processes

Even though the custom device 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:

  1. Old problem closed with the old process
  2. New problem opened when the certificate issue is detected again

📝Summary

Dynatrace’s problem lifecycle for certificate issues depends on two key factors:

1. Certificate Check Interval

  • Determines how often Dynatrace validates certificates
  • Controls how long certificate problems remain open
  • Influences how quickly problems close after renewal

2. Process Instance Status

  • Certificate problems are tied to the specific process ID
  • Restarts or crashes automatically close existing problems
  • New problems may appear during the next check if the issue persists
#SSLCertificates #ProblemDetection #ProcessMonitoring 
 
Happy Dynatracing!!!
aravind
0 REPLIES 0

Featured Posts