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

Add devices dependency with another device for alerts #3951

Closed
1 task done
JaJe92 opened this issue Oct 27, 2023 · 2 comments
Closed
1 task done

Add devices dependency with another device for alerts #3951

JaJe92 opened this issue Oct 27, 2023 · 2 comments
Labels
feature-request Request for new features to be added

Comments

@JaJe92
Copy link

JaJe92 commented Oct 27, 2023

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

Add specific devices dependent on a specific device if that device goes down.
Basically, Let's say I monitor a managed switch to be always UP and I have 4-5 devices behind that switch. If the switch goes down, I don't receive one alert but 5-6 alerts as all devices behind that switch also appear to be offline.

✔️ Solution

I suggest adding some sort of dependency tree for cases like this to be easy to monitor if the issue is on the node (switch/router) or not.

❓ Alternatives

No response

📝 Additional Context

No response

@JaJe92 JaJe92 added the feature-request Request for new features to be added label Oct 27, 2023
@CommanderStorm
Copy link
Collaborator

I think this is a duplicate of #2487 #2348 #2335
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

Note that our contribution guide can be found here and that we are open to contributions if you adhere to this

Note that #1236 is stalled because it has not been updated to work with grouped monitors ⇒ discussing a reattempt via the paths in our contribution guide is possible

@CommanderStorm
Copy link
Collaborator

@JaJe92
We are consolidating duplicate issues a bit to make issue management eazier.
I think, we should track this issue in #1089 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
=> I am going to close this as a duplicate

@CommanderStorm CommanderStorm closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

2 participants