Your Certificate Monitoring Can Work Perfectly and You Can Still Have an Outage
Expiration monitoring sounds like a solved problem.
If a certificate expires in 30 days, send an alert. If an API key expires next month, notify the owner. If a license is approaching renewal, put it on somebody's dashboard.
That was roughly how we thought about expiration management when we started building TokenTimer.
Then we spent more time working with TLS certificates and ran into an uncomfortable reality: you can build perfectly good expiration monitoring and still let a certificate expire.
The alert can fire exactly when it should, the right engineer can receive it, and the dashboard can clearly show that something needs attention. Even then, you can still end up with a production outage.
The reason is simple. Monitoring tells you that something needs to happen, but it does not actually make it happen.
That distinction changed how we think about expiration management.
Expiration Data Is Usually Scattered Everywhere
...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
