Programmatic incidents
When a monitor detects trouble (respecting your confirmation settings and any keyword/SSL checks), Phare springs into action by creating an incident. Each incident is automatically linked to the affected monitor and includes detailed information about what went wrong. Right away, your team gets notified through your configured alert rules, no manual intervention required. Programmatic incidents track the entire lifecycle from detection through resolution, giving you a complete picture of what happened during the outage.Manual incidents
Sometimes you need to create an incident even when your monitors haven’t detected a problem. Perhaps a customer reported an issue with a service you’re not actively monitoring, or you want to proactively communicate about planned maintenance. Phare makes it easy to create incidents manually:- Select the affected monitor(s)
- Set the impact level
- Add a descriptive title
- Include details about the situation
Incident recovery
When your service recovers (again, respecting your recovery confirmation settings), Phare automatically resolves the incident and lets your team know through your alert rules.Impact
Not all incidents are created equal. That’s why Phare lets your team classify incidents by their impact level:- Unknown: Still investigating, not sure how bad it is
- Operational: False alarm—everything’s working as expected
- Maintenance: Planned downtime for heavy-duty updates
- Degraded performance: Things are slower / working less well than usual
- Partial outage: Some users are affected or certain features are down
- Major outage: Everything is on fire, users can’t access the service or are severely impacted
Event timeline

Incident comments
Team members can add private comments to share insights or document solutions, helping everyone resolve issues faster. These internal notes are perfect for:- Documenting troubleshooting steps
- Sharing relevant links to logs or dashboards
- Coordinating response efforts between team members
- Recording root cause analysis findings
Incident updates

- What’s happening with the incident
- What you’re doing to fix it
- When they can expect resolution
- Workarounds they can use in the meantime