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

Downsample historical data #54

bergie opened this issue Jul 20, 2017 · 2 comments

Downsample historical data #54

bergie opened this issue Jul 20, 2017 · 2 comments


Copy link

bergie commented Jul 20, 2017

Currently we always store datapoints as they come in, and query at full resolution. With certain kinds of sensors this can become heavy.

We should implement downsampling for historical data, and set a retention policy on the full resolution tables

Copy link

baccenfutter commented Jul 22, 2017

Why don't you simply pump the data into RRDs? I mean, thinning out metrics is a problem that has been solved generically pretty well. Why reinvent the wheel?

EDIT: Ah, my bad. The sole idea is to use InfluxDB, I take it.

Copy link

You can possibly handle the downsampling directly in the InfluxQL query. For example, downsampling to reading only every 30 seconds would look something like:

SELECT FIRST(field) FROM database..measure
WHERE time >= start AND time <= end
GROUP BY time(30s)

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

No branches or pull requests

3 participants