27 Jan 2026
03:59 PM
- last edited on
28 Jan 2026
08:13 AM
by
MaciejNeumann
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.
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.
If the check interval is 24 hours, any certificate problem will remain open for at least 24 hours.
Dynatrace ties certificate problems to the specific process instance (process ID) from which the certificate was discovered.
This means if the monitored process is:
…before the next certificate check runs, Dynatrace will automatically close the existing problem, because the original process no longer exists in the environment.
During the next certificate check interval:
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:
Dynatrace’s problem lifecycle for certificate issues depends on two key factors:
Featured Posts