Keep it renewing · 7.9
What to monitor
Create at least one alert profile with Trigger: Cycle and switch on Failed issue / renew, Certificate expiring soon, Failed health check, Deploy warnings and Failed deploy, and under System the entries Cycle finished with failures and Service failed. Certificate expiring soon follows the certificate held on the targets, so a certificate that was renewed but not yet deployed still warns from the certificate the target is actually serving. If neither event 1102 nor 1106 appears for more than a day, the cycle did not run. Public ACME providers do not warn you before a certificate expires. The alerts of TLSPilot are that warning. Alert channels are available from the Standard edition, see chapter Optional features.
| Event | Level | Meaning |
|---|---|---|
| 1102 | Information, Warning | Deployment & health cycle completed. Warning if an issue, a renewal or a deployment failed or warned. The cycle alert counts deployments and health checks only. |
| 1106 | Warning | Deployment & health cycle skipped, for example because the license is expired. |
| 1103 | Error | Deployment & health cycle failed. |
| 1213 | Error | Issue or renewal failed. |
| 1221 | Information | Immediate renewal because the CA pulled the window forward and the emergency switch is on. |
| 1302 | Error | Deployment target failed. |
| 1305 | Warning | Deployment completed with a warning. |
| 1322 | Error | Health check of a target failed. |
A cycle that finds a certificate busy tries that certificate again after 30 seconds, up to 20 times. Run deployment & health cycle now is rejected while a cycle is running.