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

Req: Ability to Not Have Local Hostname in Outputs #848

Closed
s1m0 opened this issue Mar 14, 2016 · 3 comments · Fixed by #901
Closed

Req: Ability to Not Have Local Hostname in Outputs #848

s1m0 opened this issue Mar 14, 2016 · 3 comments · Fixed by #901

Comments

@s1m0
Copy link

s1m0 commented Mar 14, 2016

My primary use-case for telegraf is to collect stats off remote appliances (storage mostly) via exec or, in the future, snmp, so the local hostname is irrelevant and confusing. It can also clash with datapoints coming from plugins.

Currently there are 2 possibilities:-

  1. Use the os.hostname() by setting hostname = "", or no hostname setting
  2. Use the supplied hostname by setting hostname = "hostname.local.com"

So as not to break current .conf files, I propose using a new boolean in the [agent] section:-
usehostname = true <<-- generate the hostname tag from the hostname parameter
usehostname = false <<-- do not generate the hostname tag

@sparrc
Copy link
Contributor

sparrc commented Mar 14, 2016

I'm going to close this because it's basically a dupe of #706, if users could filter out any tag, then they could filter the hostname tag out of all of their metrics.

@sparrc sparrc closed this as completed Mar 14, 2016
@s1m0
Copy link
Author

s1m0 commented Mar 14, 2016

..IF users could filter - which we don't and anyway, adding a tag then filtering it out is a waste of resources and makes configuration more complicated.

@sparrc
Copy link
Contributor

sparrc commented Mar 15, 2016

okay, fair enough, I'll keep this issue open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants