SSL monitoring
SSL monitors connect to your host and port (for example exemplar.dev:443 on a set check interval), validate the certificate, and surface expiry, issuer, subject, and serial details. The timeline and check history show repeated successful checks with days-to-expire on each row so you can audit TLS health over time.
Example: SSL monitor with expiry date, issuer/subject, and hourly check history.
Video: SSL certificate monitoring and email alerts
Step-by-step guide
Work in the Exemplar console .
-
Open SSL / certificate monitoring — Go to the area where SSL, TLS, or certificate monitors are created and managed.
-
Create an SSL monitor — Add a monitor for your host and port (for example
api.example.com:443). Set a check interval that fits your risk tolerance (more frequent checks catch misconfigurations sooner; very tight intervals add load). -
Confirm what gets validated — Ensure the product is checking the certificate chain, expiry, and any hostname or SAN rules you care about. Note the days to expiry and issuer / subject shown in the UI so they match expectations.
-
Use timeline and history — Review the timeline and check history so you see a steady pattern of successful checks and can spot intermittent TLS issues or clock skew.
-
Attach to your operational view (optional) — Add the SSL monitor to a service board or dashboard so certificate health sits next to uptime and other signals.
-
Configure email alerts — In notifications, alerts, or destinations, add email for this monitor or for certificate events. Choose addresses (for example platform or security DL, on-call), and when to notify (for example approaching expiry, renewal failure, or check failure). Complete any verification or subscription steps the UI requires.
-
Test end-to-end — Use a test email or a staging host with a short-lived cert if your process allows, and confirm messages include the right host, expiry context, and links back to the monitor.
-
Document ownership — Record who owns DNS and certificate renewal, who receives email, and your internal renewal lead time so alerts stay actionable before expiry.
Blog
- Why uptime and synthetic monitors still matter in the age of APM — How SSL checks and other probes sit alongside APM and telemetry.