β οΈ Please verify that this feature request has NOT been suggested before.
[X] I checked and didn't find similar feature request
π·οΈ Feature Request Type
UI Feature
π Feature description
I would like to propose a feature that could improve the accuracy and relevance of our monitoring system.
Feature Description:
Currently, if a monitor has a single failed response out of several (say one out of five), the system immediately treats this as a downtime incident. I suggest that the uptime status should still be marked as "operational" in such cases and not count towards the downtime percentage until a defined number of failed responses is reached.
Benefits:
Accuracy: This would reduce the number of false alarms.
Reliability: Monitoring results would more accurately reflect the true status.
Flexibility: It would allow companies to fine-tune alert thresholds according to their specific needs.
βοΈ Solution
Possible Implementation:
Introduce a setting that allows users to define an acceptable number of failed responses before the system marks the monitor as down.
The status would only change to "down" after the specified number of failed responses occur.
β οΈ Please verify that this feature request has NOT been suggested before.
π·οΈ Feature Request Type
UI Feature
π Feature description
I would like to propose a feature that could improve the accuracy and relevance of our monitoring system.
Feature Description: Currently, if a monitor has a single failed response out of several (say one out of five), the system immediately treats this as a downtime incident. I suggest that the uptime status should still be marked as "operational" in such cases and not count towards the downtime percentage until a defined number of failed responses is reached.
Benefits:
βοΈ Solution
Possible Implementation:
β Alternatives
No response
π Additional Context
No response