We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Other
Hellow guys! Can you add tags to Prometheus metrics as new lable?
Now I am doing monitoring in zabbix for many teams in our company who are responsible for different sites.
Of course, zabbix allows you to create a lot of fake entities (hosts) and metrics on them can be filtered in discovery by regexp.
BUT I would still like to send notifications from one host based on item tags, and not to produce many fake hosts and rely on host group tags.
Adding tags to Prometheus metrics labels.
Logical separation: one team responsible for the site - one host (in zabbix)
Tags to metrics
The text was updated successfully, but these errors were encountered:
I think this is duplicate of #680 and would be solved by #898.
Sorry, something went wrong.
No branches or pull requests
🏷️ Feature Request Type
Other
🔖 Feature description
Hellow guys! Can you add tags to Prometheus metrics as new lable?
Now I am doing monitoring in zabbix for many teams in our company who are responsible for different sites.
Of course, zabbix allows you to create a lot of fake entities (hosts) and metrics on them can be filtered in discovery by regexp.
BUT I would still like to send notifications from one host based on item tags, and not to produce many fake hosts and rely on host group tags.
✔️ Solution
Adding tags to Prometheus metrics labels.
❓ Alternatives
Logical separation: one team responsible for the site - one host (in zabbix)
📝 Additional Context
Tags
![TAG](https://user-images.githubusercontent.com/28865504/181081010-2dc8a64a-2e88-43b8-a4a6-381fb9d8db49.png)
![like this](https://user-images.githubusercontent.com/28865504/181081980-ebd36a08-7377-4dde-9e08-f4b4d53b06ad.png)
to metrics
The text was updated successfully, but these errors were encountered: