Incidents
How incidents open and resolve on their own, and what an incident records.
An incident is one outage of one camera, from the moment OpticWatch decides the camera is down until it is working again. Incidents are opened and resolved by monitoring itself; there is nothing to open or close by hand. Every edition records them, including Free.
How an incident opens and resolves
- A camera fails several checks in a row (3 by default) and becomes Offline. An incident opens, with the reason for the failure.
- While the camera stays down, each further failed check updates the incident: its latest reason and its count of failed checks.
- The camera succeeds several checks in a row (2 by default) and becomes Healthy. The incident is resolved, and its duration is recorded.
A single failed check never opens an incident. The thresholds are under Settings, Monitoring.
What an incident records
- Camera and site
- Which camera went down, and where.
- Status
- Open or Resolved.
- Started and resolved
- When it began and ended, and so how long it lasted.
- Initial reason
- Why the camera was marked Offline.
- Latest reason
- The most recent failure, which can differ, for example a timeout that becomes a refused connection.
- Failed checks
- How many checks failed during the incident.
Finding incidents
- Dashboard shows what is open right now.
- Incidents lists them all. Filter by Open, Resolved or All, and by site.
- Each camera's page has its own Incident history.
Incidents are kept until you delete the camera they belong to. Deleting a camera deletes its incident history with it.
Being notified
Pro and Integrator can notify you by email or webhook when an incident opens and when it is resolved. See Email and webhook alerts. On Free, incidents are recorded and shown in OpticWatch but not sent anywhere.