-
-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] Add information about default alert settings #611 #637
Conversation
- **High CPU Usage**: Triggered if CPU usage exceeds **90%** for more than **15 minutes**. | ||
- **Iperf3 Bandwidth Drop**: Triggered if **TCP bandwidth** is less than **10Mbit/s** for more than **2 days**. | ||
|
||
These settings can be customized through the device page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't you noticed that this section is inserted in the middle of the explanation of the iperf3 settings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @nemesifier,
I apologize for my oversight in placing the "Default Alert Settings" section in the middle of the Iperf3 settings documentation. I have now reorganized the document structure to improve readability and flow.
I have updated it:
- Introduction to device checks and alert settings
- Default alert settings (moved to the beginning)
- Adding custom checks
- Customizing specific checks (Iperf3 example)
Please review the changes and let me know if any further improvements are needed.
Thank you for reviewing it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I read more closely what's written in there and it looks completely made up. Are you using generative AI to do this?
The default alerts include: | ||
|
||
- **Ping Loss**: Triggered if packet loss exceeds **30%** over **5 minutes**. | ||
- **High Latency**: Triggered if response time is greater than **200ms** for **10 consecutive pings**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please point out the configuration file from which you're getting this?
|
||
- **Ping Loss**: Triggered if packet loss exceeds **30%** over **5 minutes**. | ||
- **High Latency**: Triggered if response time is greater than **200ms** for **10 consecutive pings**. | ||
- **Low Disk Space**: Triggered if available disk space falls below **10%**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does the point below mention tolerance while this doesn't?
|
||
The default alerts include: | ||
|
||
- **Ping Loss**: Triggered if packet loss exceeds **30%** over **5 minutes**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please point out the configuration file from which you're getting this?
Checklist
Reference to Existing Issue
Closes #611.
Description of Changes
This PR adds a new section explaining the default alert settings in OpenWISP Monitoring. The updated documentation includes:
These changes enhance the documentation by making it easier for users to understand the built-in monitoring alerts and their behavior.
@nemesifier kindly review it