Overview
Events configurations allow for the management of event triggers severity and relevancy time, providing the freedom to pick and chose which system events matter most.
- 1
- Search bar
- 2
- Sort by
- 3
- Action cogs
7.3.1 About events configurations
Severity and Auto ageing
Severity makes it possible to influence how much certain issues affect the health score when they appear. Based on a scale from 0.1 - 1.0, where 0.1 greatly affects the health score and 1.0 slightly affecting the health score. This makes the system more transparent about the frequency of issues that are deemed more or less important.
Auto ageing dictates how long the notification about the issue persists and affects the health score. The time can only be set on predefined amounts of time. This can be used to track the frequency of certain issues during a given time period.
Default events and their settings
| EVENTS | SEVERITY | AUTO AGEING |
| Button – pairing failed | 0.5 (Warning) | 48 hours |
| Button – pairing success | 1.0 (Info) | 24 hours |
| Display connected | 1.0 (Info) | 24 hours |
| Display disconnected | 0.2 (Critical) | 24 hours |
| Display – edid not found | 0.3 (Critical) | 24 hours |
| Display – resolution change failed | 0.3 (Critical) | 24 hours |
| Firmware update – failed | 0.4 (Warning) | 72 hours |
| Firmware update – success | 1.0 (Info) | 24 hours |
| Peripheral connected | 1.0 (Info) | 24 hours |
| Peripheral disconnected | 0.2 (Critical) | 24 hours |
| System – CPU critical temperature reached | 0.1 (Critical) | 8 hours |
| System – fan stopped | 0.2 (Critical) | 8 hours |