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

Any plan to support multiple installation? #105

Open
bastianb opened this issue Jul 16, 2018 · 5 comments
Open

Any plan to support multiple installation? #105

bastianb opened this issue Jul 16, 2018 · 5 comments

Comments

@bastianb
Copy link

Hi, do you plan to implement multiple installation to have more than one telegraf running on the machine ?

@htj
Copy link
Contributor

htj commented Feb 19, 2020

Hi, we have the same issue as well. It mostly due to telegraf output all inputs to all outputs which is not always desirable.

Right now we solve it by dumping in another config file, and running a seperate telegraf instance.

@dhoppe
Copy link
Member

dhoppe commented Feb 19, 2020

Why exactly do you need multiple Telegraf instances? As far as I know, you can route the inputs based on a tag to a specific output.

@htj
Copy link
Contributor

htj commented Feb 20, 2020

@dhoppe Thanks, I was not aware of that feature.

We do have another case, where we have some system that updates counters every 30 seconds, which we need collect.

And then we have some other collectors on the same hosts that pull data from ~70 system that updates continously. Here we need to add some collection jitter to avoid tipping over the collector VM, and it is not currently possible to have only have collection jitter on some inputs (but I guess that is a telegraf feature request).

@dhoppe
Copy link
Member

dhoppe commented Feb 20, 2020

Telegraf uses an interval of 10s by default, but you can override this for a specific plugin. For example:

[[inputs.snmp]]
  interval = "1m"

Correct. As far as I know, you can not configure a different jitter for a specific plugin.

@htj
Copy link
Contributor

htj commented Feb 20, 2020

I'm aware of the interval option (we use it widely), but jitter is the problem.

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

No branches or pull requests

3 participants