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

writing to replicated influxdb instances #4

Open
donaldleckie opened this issue Oct 15, 2018 · 0 comments
Open

writing to replicated influxdb instances #4

donaldleckie opened this issue Oct 15, 2018 · 0 comments

Comments

@donaldleckie
Copy link

donaldleckie commented Oct 15, 2018

Hi Florian,
In our configuration, our monitoring is replicated across 2 physical datacentres with replica InfluxDB instances. Our regular application nodes emit metrics to both InfluxDBs simultaneously.
I'd like to have our kafka cluster also report to both InfluxDBs as well - would you be happy to receive a pull request which implements this for everyone's benefit?

Separately, because our kafka nodes are updated/restarted via a rolling upgrade, the current implementation has each node recording data in the InfluxDB with different offsets - again, would you be OK to receive a pull request which aligns them to the reporting period? For example, reporting every 60 seconds would have reports created at the top of each minute.
One SNAFU on this topic is that the InfluxReporter's parent is an AbstractPollingReporter which unfortunately has a built-in time drift because it uses the ScheduledExecutorService.scheduleWithFixedDelay rather than scheduleWithFixedPeriod, which is probably what it meant to use (I guess this is a bug in already-old code). This should be OK, just means that the InfluxReporter has to extend AbstractReporter instead.

Appreciate your thoughts.
Donald

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

1 participant