Feature #891
Keep a duration for error events
| Status: | Resolved | Start date: | 08/29/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | Server | Spent time: | - | |
| Target version: | 2.0.0-beta9.1 | |||
| Release Blocker: | No | Operating System: |
Description
Error events, such as "camera not found", should be recorded as a single event with a duration, rather than a series of periodic events. There is no need for a maximum duration. The event would end when the problem is no longer occurring or has changed.
This will enable a nice display of errors in a timeline view on the client, and allow the client to easily display if a device is currently in some error state.
Subtasks
History
Updated by Curtis Hall 9 months ago
- Assignee changed from Ben Collins to Veaceslav Falico
- Target version changed from 2.x (Staging) to 2.0.0-beta9
Updated by Curtis Hall 6 months ago
- Target version changed from 2.0.0-beta9 to 2.0.0-beta9.1
Updated by John Brooks 5 months ago
- Assignee changed from Veaceslav Falico to John Brooks
Updated by John Brooks 5 months ago
- Status changed from Assigned to Resolved