mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
URL Tags to Prometheus metrics :) #1292
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1292
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Freezepop on GitHub (Jul 26, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ 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


to metrics
@spali commented on GitHub (Jan 18, 2023):
I think this is duplicate of #680 and would be solved by #898.