Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upRemote storage adaptor reads influxDB data only from the default retention policy #2779
Comments
juliusv
referenced this issue
May 29, 2017
Merged
Fix InfluxDB retention policy usage in read adapter #2781
This comment has been minimized.
This comment has been minimized.
juliusv
closed this
in
#2781
May 29, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
sesto commentedMay 29, 2017
What did you do?
I have been playing around with the remote storage adaptor to see how the export of data into influxDB works. I have created 2 retention policies "low_density" and "high_density" in influxDB, with the "high_density" policy set as default.
I start the remote storage adaptor with the parameter
-influxdb.retention-policy=low_densityWhat did you expect to see?
I expect that the adaptor will write/read to/from the
low_densityretention policyWhat did you see instead? Under which circumstances?
The adaptor writes data to the
low_densityretention policy as expected but reads data from the defaulthigh_densityretention policyBelow is influxDB log:
Environment
OS X 10.11.4
Prometheus and influxDB are run as docker containers, remote storage adapter as a go application on os, go version 1.8.1
Darwin 15.4.0 x86_64
Alertmanager version:
insert output of
alertmanager -versionhere (if relevant to the issue)Prometheus configuration file: