You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to work better with tags instead of using groups or the host's names to select group/host specific items.
Some other observability solutions support boolean operators for Tags. For example, if I want an specific item that has both the "env: prod" and the "component: cpu" tags, I would use "component:cpu AND env:prod" on the Tags field in the Query.
Another thing is item inheriting the host's tags, so that I can use these Tag Boolean operators even if the tags are associated to the host.
I know that, through the API (which the datasource uses), we can get the hosts, and then the items associated with them, so I think it would be pretty great that when doing a host.get, it enables the selectTags flag, and all the tags that are associated with the host are then pushed to the tags array for each of the host's items.
Working with tags also saves us the time of creating a group for each possible combination of metadata the host can have (for example the host's environment, project name, service associated with it, team associated with it, etc). And since the items are also inheriting the host's tags, it also inherits this type of metadata.
Example:
Example with Wildcard operator + Boolean:
The text was updated successfully, but these errors were encountered:
LinekerCalseverini
changed the title
Support for Tag Boolean Operators and Host Tag Inheritance
Feature Request: Support for Tag Boolean Operators and Host Tag Inheritance
Oct 1, 2024
I wanted to work better with tags instead of using groups or the host's names to select group/host specific items.
Some other observability solutions support boolean operators for Tags. For example, if I want an specific item that has both the "env: prod" and the "component: cpu" tags, I would use "component:cpu AND env:prod" on the Tags field in the Query.
Another thing is item inheriting the host's tags, so that I can use these Tag Boolean operators even if the tags are associated to the host.
I know that, through the API (which the datasource uses), we can get the hosts, and then the items associated with them, so I think it would be pretty great that when doing a host.get, it enables the selectTags flag, and all the tags that are associated with the host are then pushed to the tags array for each of the host's items.
Working with tags also saves us the time of creating a group for each possible combination of metadata the host can have (for example the host's environment, project name, service associated with it, team associated with it, etc). And since the items are also inheriting the host's tags, it also inherits this type of metadata.
Example:
Example with Wildcard operator + Boolean:
The text was updated successfully, but these errors were encountered: