prometheus-boshrelease
prometheus-boshrelease copied to clipboard
integrate with influxdb for long term storage
Hi,
I've been looking at using influxdb to provide long term storage. The prometheus job already includes properties for remote_write and remote_read.
Would you be open to a PR that would include the following.
- operator file to deploy an influxdb instance
- update
prometheus.ymltemplate from prometheus job to optionally setremote_writeandremote_readbased on BOSH link data from the influxdb instance.
NOTE: i did spend time looking at building a BOSH job for remote_storage_adapter based on https://github.com/prometheus/prometheus/tree/release-2.1/documentation/examples/remote_storage/remote_storage_adapter but it now appears that influxdb 1.4.x supports the prometheus read/write natively.
Cheers, Michael
@m-richo What influxdb bosh release do you plan to add at the op-file?
i had a look around and thought the following from the concourse folk was most active https://github.com/concourse/influxdb-boshrelease
it's a fork, but they don't appear to be upstreaming.
I've raised a PR to them to add BOSH links and intended to raise another to upgrade influxdb from 1.3 to 1.4.3 (current) which supports prometheus remote storage natively.
Sounds good!
HI, did u have tried to integrate promethsu2 with influxdb successfully? and can someone share your manifests it possible?
@Alexvianet I have never tried it, maybe @m-richo has updates?
works well with https://github.com/cloudfoundry-community/influxdb-boshrelease prometheus2 job:
properties:
prometheus:
remote_write:
- url: http://influxdb:8086/api/v1/prom/write?u=user&p=pass&db=yourdb
remote_read:
- url: http://influxdb:8086/api/v1/prom/read?u=user&p=pass&db=yourdb
Thanks @Alexvianet. Willing to contribute an op-file to enable this?
I am planning to test this in one of our environments, I will create a PR with an Ops File if this is not done until then.
This issue is stale because it has been open 60 days with no activity. Comment or this will be closed in 5 days.
This issue was automatically closed because it has been stalled for 5 days with no activity.