Incidents
Incidents are an ops layer on top of alerts — investigate, identify, monitor recovery, and resolve. Quiet empty desks mean no open incidents.
What incidents are#
The incident desk tracks investigation state for failures that already opened alerts. It does not replace monitoring or invent a second alert engine.
Product path: /app/incidents.
Alert to incident#
When an alert opens, Mydle opens or attaches an incident for that project. Repeated failures for the same outage deduplicate onto the existing open alert and incident instead of creating duplicates.
Details: Alerts & Incidents.
Lifecycle#
The only supported lifecycle is investigating → identified → monitoring → resolved. See Incident Lifecycle.
Notifications#
Alert and incident events fan out through configured channels (email, Slack, Discord, Teams, and generic webhooks). See Notifications.
Status pages#
Public customer status pages live under incidents. Guide: Status Pages.
Impact#
Incident impact shows measurable telemetry attached by correlation IDs — never invented user counts. See Incident Impact and the broader Impact section.
Plans#
Incidents require Pro (incidents). Free has no incident desk.
Limitations
- Lifecycle is fixed — there is no reopen path after resolve.
- Empty lists mean quiet systems, not fabricated zero-severity health.
- Native PagerDuty / Opsgenie connectors are not in the channel kind enum.