-
Notifications
You must be signed in to change notification settings - Fork 43
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
[dev.icinga.com #8589] Introduce a new node type: FilteredObjectsNode #14
Labels
enhancement
New feature or improvement
Comments
Updated by tgelf on 2015-03-09 13:43:56 +00:00 It should be possible to decide whether the filter should be based on hosts, services or both. |
Updated by mfriedrich on 2015-06-24 13:35:20 +00:00
|
Updated by tgelf on 2015-12-16 17:45:31 +00:00
|
Duplicate of #328 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8589
Created by tgelf on 2015-03-03 15:42:42 +00:00
Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2015-06-24 13:35:20 +00:00 (in Redmine)
I want to be able to create a nodes in a way allowing me to not define objects one by one but by assigning a specific monitoring object filter like host=db*&service=ping. While this first part will be pretty easy, it doesn't suffice. Most people will very soon feel the desire to automagically create multiple node definitions based on specific patterns.
Immagine a structure like this one:
You cannot solve this by just stating something like:
This would lead to a completely different logic and would not be what you intended to achieve. One possible way to configure what we had in our mind could look as follows:
Best,
Thomas
Relations:
The text was updated successfully, but these errors were encountered: