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

Allow specifying a statsd namespace #898

Closed
grantr opened this issue Apr 30, 2015 · 2 comments · Fixed by #902
Closed

Allow specifying a statsd namespace #898

grantr opened this issue Apr 30, 2015 · 2 comments · Fixed by #902
Labels
type/enhancement Proposed improvement or new feature

Comments

@grantr
Copy link

grantr commented Apr 30, 2015

It's great that Consul can emit statsd metrics, but without a configurable namespace they aren't as helpful as they could be.

Currently, the namespace varies between consul and consul.<fqdn>. A configuration parameter like statsd_namespace would allow separate consul deployments to each write separate stats.

@ryanuber ryanuber added the type/enhancement Proposed improvement or new feature label May 3, 2015
@ryanuber
Copy link
Member

ryanuber commented May 3, 2015

Thanks for the suggestion, marked as an enhancement!

@pwielgolaski
Copy link

I looked at the PR that close this issue and it is very misleading.

statsite_prefix The prefix used while writing all telemetry data to statsite. By default, this is set to "consul".

Documentation mention only statsite, but in fact in code this value can be used also for Statsd& DataDog

metricsConf := metrics.DefaultConfig(config.StatsitePrefix)

I think name should be change or at least description for option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Proposed improvement or new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants