Source
Alerting, escalation & on-call — found from sitemap — Phare Uptime
Checked for Phare Uptime on 1 Nov 2026
- Page
- https://docs.phare.io/uptime/alerting
- Checked
- 1 Nov 2026, 10:42 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:9e611ab91d0ee3c50dcb35cf1b2c555802c8d5388796b60f391cd657adf8bad1
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Alert rules elements Report an error
“Each rule defines four key elements: Event: What triggers the alert (like a monitor failing or a certificate nearing expiration) Scope: Where the rule applies (organization-wide or just in specific projects) Rate limit: How often the notification can be sent (preventing notification fatigue) Integration: Where to send the alert (email, Slack, Discord, etc.)”
-
Monitor events Report an error
“Monitor created uptime.monitor.created Sent when a new monitor is created, great for logging or auditing purposes. Monitor deleted uptime.monitor.deleted Sent when a monitor is deleted, great for logging or auditing purposes.”
-
Certificate events Report an error
“Monitor certificate discovered uptime.monitor_certificate.discovered Sent when a new SSL certificate is discovered on a monitor, useful for tracking changes and certificate renewal confirmation. Monitor certificate expiring uptime.monitor_certificate.expiring Sent when a monitor’s SSL certificate is nearing expiration, based on a configurable threshold.”
-
Incident events Report an error
“Incident created uptime.incident.created Sent when a new incident is created, this is the main alert for incident management. Incident propagated uptime.incident.propagated Sent when an incident propagates to an additional monitor. Requires smart incident merging to be enabled. Incident partially recovered uptime.incident.partially_recovered Sent when a monitor recovers but the incident is still ongoing due to other affected monitors. Requires smart incident merging to be enabled. Incident recovered uptime.incident.recovered Sent when an incident has fully recovered, indicating that all affected monitors are back to normal. Incident comment created uptime.incident_comment.created Sent when a new comment is added to an incident, useful for keeping team members informed of updates and discussions. Incident update published uptime.incident_update.published Sent when a new public incident update is published on a status page, useful for notifying stakeholders and users about the incident status.”
-
Maintenance window events Report an error
“Maintenance window in progress uptime.maintenance_window.in_progress Sent when a maintenance window starts, notifying teams that planned downtime has begun. Maintenance window completed uptime.maintenance_window.completed Sent when a maintenance window is finished, confirming normal operations have resumed. Maintenance window cancelled uptime.maintenance_window.cancelled Sent when a scheduled or in-progress maintenance window is cancelled.”
-
Alert rule scope Report an error
“Organization: Catch all matching events across your entire organization Project: Focus only on events within specific projects”
-
Alert rate limiting Report an error
“Phare lets you set limits on how frequently a notification can be sent. Even if an event triggers multiple times, you’ll only be notified based on your preferred cadence, like at most once every 10 minutes.”
-
Notification channels Report an error
“Connect any integration to your alert rules to receive notifications through your preferred channels. Create as many alert rules as you need”
-
Duplicate alert rules Report an error
“To send the same alerts to another channel, duplicate an alert rule from its actions menu in the alert rules list. The new rule starts with the same event, scope, filters and rate limit: choose another integration and create it.”
-
Uptime alerting examples Report an error
“Integration: Where to send the alert (email, Slack, Discord, etc.)”
-
Uptime terraform Report an error
“Terraform”
-
Uptime ansible Report an error
“Ansible”
-
Uptime nixos Report an error
“NixOS”
Scores citing this record
- The Agency Developer Alerting, escalation & on-call
- The Customer Support Lead Alerting, escalation & on-call
- The E-Commerce Operations Manager Alerting, escalation & on-call
- The SaaS Platform Engineer Alerting, escalation & on-call
- The Information Security Officer Alerting, escalation & on-call
- The Skeptic Alerting, escalation & on-call