Skip to content
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

[Feat]: Reachability notifications Enhancements #1027

Closed
sashwathn opened this issue Jun 17, 2024 · 0 comments
Closed

[Feat]: Reachability notifications Enhancements #1027

sashwathn opened this issue Jun 17, 2024 · 0 comments

Comments

@sashwathn
Copy link

Problem

The reachability notifications can be spammy when there is a network issue between Netdata agent (parent or child) and the cloud. We need to find a solution to make it configurable and group the notifications.

Description

Netdata needs to support following functionality on the reachability notifications to reduce the spam:

  • User Configurable timeouts for reachability notifications.
  • In a scenario where the child nodes are not connected to cloud (directly) and are connected via a parent (or a parent cluster), If the connectivity between the parent (or parent cluster) and the cloud is down, coalesce / group the notifications (for the parent and all its children)
  • If one of the parents is connected to the cloud, reachability notifications should not be triggered for all the children (I think this is already supported but good to check).

cc: @car12o @ktsaou @ralphm @stelfrag @Ferroin

Importance

must have

Value proposition

  1. Reduces spammy notifications
  2. Provides more control to the user based on their knowledge of their own network.

Proposed implementation

  • User Configurable timeouts for reachability notifications.
  • In a scenario where the child nodes are not connected to cloud (directly) and are connected via a parent (or a parent cluster), If the connectivity between the parent (or parent cluster) and the cloud is down, coalesce / group the notifications (for the parent and all its children)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants