-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
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
[feature] - add namespace label to nomad.client.allocs.* #5554
Comments
Agreed. I'll take this to the team, this should be pretty easy to get in. |
@cgbaker Any updates on this? |
@henrikjohansen , we didn't get it in for the upcoming 0.9.2, but we have put it on the list for 0.9.3. apologies for the delay on this. |
@henrikjohansen , merged, will be part of upcoming 0.9.4. thank you for your patience. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Using namespaces it's suddenly possible to have multiple jobs with the same jobname running.
In our case, the Telemetry data is made available to service owners & developers but without some unique identifier we can no longer route those events correctly :(
I would like to propose adding the namespace as an additional label to all nomad.client.allocs.* metrics in order to make ☝️ possible.
Example :
nomad.client.allocs.<Namespace>.<Job>.<TaskGroup>.<AllocID>.<Task>.metric
The text was updated successfully, but these errors were encountered: