-
Notifications
You must be signed in to change notification settings - Fork 4
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 the ability to filter monitors #423
Labels
Milestone
Comments
NassimBtk
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
labels
Sep 23, 2024
TNohaic
added a commit
that referenced
this issue
Oct 10, 2024
TNohaic
added a commit
that referenced
this issue
Oct 11, 2024
TNohaic
added a commit
that referenced
this issue
Oct 11, 2024
TNohaic
added a commit
that referenced
this issue
Oct 11, 2024
NassimBtk
added a commit
that referenced
this issue
Oct 11, 2024
…-to-filter-monitors Issue #423: Add the ability to include or exclude monitored instances
NassimBtk
changed the title
Ability to filter monitors
Add the ability to filter monitors
Oct 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Needs
Add the ability to include or exclude monitored instances.
Specification
The user should be able to specify a set of monitors to be included or excluded.
A match type using
+
and!
notations should be implemented.The engine/hardware strategies (Discovery, Collect, Simple, Hardware.*) need to be updated in order to apply the filter.
We need to provide a filtering section under the resource, resource group or even globally in metricshsub.yaml.
Add a new configuration property in metricshub.yaml:
monitorFilters
.The text was updated successfully, but these errors were encountered: