Escalating Downtime Issues - Documentation

Creating multiple contacts and setting up Alerts with different escalation levels can be useful for managing downtime issues effectively.

Create multiple contacts, each representing a different level of escalation.

• Primary Contact: This could be the first person or team to be notified of any issues.
• Secondary Contact: This could be a backup person or team to be notified if the primary contact doesn't respond within a certain timeframe.
• Tertiary Contact: This could be a higher-level support or management team to be notified if the issue persists and requires urgent attention.

Configure alert settings for each escalation level.

• Primary Contact: Set the "Alert after" to 1 check, meaning they will be alerted immediately when an issue is detected.
• Secondary Contact: Set the "Alert after" to 2 checks, indicating they will be alerted if the issue persists for two consecutive checks.
• Tertiary Contact: Set the "Alert after" to 3 or more checks, signifying they will be notified only if the issue persists for an extended period.

With this setup, the monitoring system will escalate alerts based on the configured escalation levels. If the issue persists beyond the specified number of checks for the primary contact, the system will escalate the alert to the secondary contact, and so on, ensuring that downtime issues are addressed promptly and efficiently according to their severity.