-
Notifications
You must be signed in to change notification settings - Fork 351
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
How to handle prometheus remote_write case with influxdb-relay #66
Comments
Run on relay server: gives:
|
Hi @Alexvianet! I have exactly same situation here and I assume Prometheus does not work with influxdb-relay at all. Assuming influxdb-relay has not been updated for 2 years now, I doubt it will work at all. P.S. At least the curl error you mentioned in the second post can be easily fixed by commenting out relay/http.go:122 function section (just for tests of course), but it won't help writing the data. |
My team is also hitting a pain point on this. I recently ditched the remote_storage_adapter in favor of the native influx support, however the relay is a must to ensure the data captured is reliable.
.. EDIT: |
Support for Prometheus remote write has been added on https://github.com/vente-privee/influxdb-relay (develop branch). Feel free to try it quickly! |
@Alexvianet Did you have the chance to try it ? We continued to improve Prometheus support on our side and we will be glad to hear from you ! :D |
sorry no, we have moved away from influxdb to thanos with s3
…On Fri, Nov 16, 2018, 18:47 Geographer ***@***.***> wrote:
@Alexvianet <https://github.com/Alexvianet> Did you have the chance to
try it ? We continued to improve Prometheus support on our side and we will
be glad to hear from you ! :D
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#66 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQrHRTD9WwZJIfFh4jPazGdkcTeKdeZ7ks5uvuwGgaJpZM4UWrOl>
.
|
how should i configure relay in prometheus case
prometheus config:
relay config:
Loadbalancer nginx config:
and get error
2018/06/01 14:08:02 [error] 10360#0: *69959 readv() failed (104: Connection reset by peer) while reading upstream, client: prometheus_host, server: relay.Loadbalancer, request: "POST /api/v1/prom/write?u=foo&p=bar&db=prometheus HTTP/1.1", upstream: "http://relay:9096/api/v1/prom/write?u=foo&p=bar&db=prometheus", host: "relay.Loadbalancer:9096"
The text was updated successfully, but these errors were encountered: