Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAre these MetaLablels like service_name all hardcoded? #4548
Comments
This comment has been minimized.
This comment has been minimized.
|
Hi, yes. These correspond to kubernetes service abstraction. This doesn't look like a bug report or feature request, but more like a question. To make your question, and all replies, easier to find, we suggest you move this over to our user mailing list, which you can also search. If you prefer more interactive help, join or our IRC channel, #prometheus on irc.freenode.net. Please be aware that our IRC channel has no logs, is not searchable, and that people might not answer quickly if they are busy or asleep. If in doubt, you should choose the mailing list. Once your questions have been answered, please add a short line pointing to relevant replies in case anyone stumbles here via a search engine in the future. |
gouthamve
closed this
Aug 28, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
etsangsplk commentedAug 27, 2018
Are metalabels like "service_name", " "service_port_name" etc, all hard coded as conventions?
Found at
prometheus/discovery/kubernetes/service.go
Line 138 in 2236bb6
serviceNameLabel = metaLabelPrefix + "service_name"
serviceLabelPrefix = metaLabelPrefix + "service_label_"
serviceAnnotationPrefix = metaLabelPrefix + "service_annotation_"
servicePortNameLabel = metaLabelPrefix + "service_port_name"
servicePortProtocolLabel = metaLabelPrefix + "service_port_protocol"