Skip to content
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

Filter allocation metrics from statsd metrics #1499

Closed
jshaw86 opened this issue Aug 2, 2016 · 4 comments
Closed

Filter allocation metrics from statsd metrics #1499

jshaw86 opened this issue Aug 2, 2016 · 4 comments

Comments

@jshaw86
Copy link

jshaw86 commented Aug 2, 2016

We would like to have a parameter to toggle off the live allocation metrics and just emit node level metrics to statsd.

Our use case for this is to leverage librato for capacity planning and sending all allocation metrics to librato is costly.

In the future we may like to target specific allocations to emit allocation level metrics out of on a on-demand basis but we could use the command line for those specific cases.

@diptanu
Copy link
Contributor

diptanu commented Aug 2, 2016

@dadgar had a good idea about making this prefix matched so that the client can publish allocation metrics for certain jobs.

@jshaw86
Copy link
Author

jshaw86 commented Aug 2, 2016

@diptanu @dadgar yea i think that would work fine.

@diptanu
Copy link
Contributor

diptanu commented Aug 3, 2016

@jshaw86 For now we have added the tunables publish_allocation_metrics and publish_node_metrics which will allow you to turn on/off this feature. Nomad Enterprise will support turning off/on metrics for individual or a group of Jobs.

@github-actions
Copy link

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants