You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 5, 2022. It is now read-only.
Hi,
I was wondering if it'd be possible to run multiple replicas of Telegraf to ensure high availability within the Kubernetes cluster.
The change for the chart should be very straightforward, but I'm not sure if there's a reason why it may not be supported.
Thanks
The text was updated successfully, but these errors were encountered:
I think this really depends on how you use telegraf and wich plugin, for example, if you use the http one that exposes a compatible influxdb API it is safe to run more of them because you will pick one.
But if you configure 2 telegraf with the Prometheus input plugin they will scrape both the same metrics and you will end up with data duplication.
In my case I'm using it as a statsd endpoint which then pushes to influxdb. I think it'd be nice to have the option to run multiple replicas in the chart. Then who doesn't need it can just stick to the default of 1 replica.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I was wondering if it'd be possible to run multiple replicas of Telegraf to ensure high availability within the Kubernetes cluster.
The change for the chart should be very straightforward, but I'm not sure if there's a reason why it may not be supported.
Thanks
The text was updated successfully, but these errors were encountered: