Alerts

TSL Monitor can be configured to generate alerts (Email, SMS and/or SNMP) when the following events occur:

TSL fetch failed (Reason: Connection with TSL resources failed).
TSL fetch failed (Reason: TSL format is invalid).
The downloaded TSL signature could not be verified for the configured TSL.
The downloaded TSL has already expired; the current TSL in the database has also expired (so now no valid TSL exists in ADSS Server for this TSL). This is a serious event as the certificates from this TSL can no longer be verified correctly by ADSS Server.
The downloaded TSL had already expired but the current TSL in the database is still valid.
(i.e. perhaps a potential problem when the current TSL expires).
Successfully download a new TSL and saved it to the ADSS Server database.
The downloaded TSL is already present in the ADSS Server database (this will be typical in situations where ADSS Server is polling more frequently for TSLs than the TSL is actually publishing).
When the Master ADSS TSL Monitor instance becomes Slave.
Internal error occurred (Reason: database not available etc.)
If the service is unable to use the log signing key at the auto-archiving time.
When archiving is successfully completed.

The system operators that will receive these alerts can be defined within the TSL Monitor management screen. Operator email and SMS details are defined within the Access Control screens as operators are registered.