-
Notifications
You must be signed in to change notification settings - Fork 939
Open
Labels
sig-issueA specific SIG should look into this before discussing at the specA specific SIG should look into this before discussing at the specspec:miscellaneousFor issues that don't match any other spec labelFor issues that don't match any other spec label
Description
What are you trying to achieve?
Open questions:
- Should we keep translating
jobandinstancetoservice.nameandservice.instance.idby default? - Should we keep dropping target_info and converting it to resource attributes?
I think the answer to (2) is yes. Even if we were to no longer export target_info from prometheus exporters, it seems like the receiver portion should still support turning those into resource attributes.
We should discuss (1). There have been cases of users being confused as to why they can't use processors on the job and instance labels. But overall, i'm not convinced that breaking users would be worth it at this point regardless of our opinions on which was less confusing.
Metadata
Metadata
Assignees
Labels
sig-issueA specific SIG should look into this before discussing at the specA specific SIG should look into this before discussing at the specspec:miscellaneousFor issues that don't match any other spec labelFor issues that don't match any other spec label
Type
Projects
Status
No status