-
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 test influxdb-relay working or not on multinode…? #77
Comments
server 1:- influxdb-realy.conf file -- toml --InfluxDB && Prometheus[[http]] Timeout for /health routeAfter this time, the host may be considered downhealth-timeout-ms = 10000 Request limiting (Applied to all backend)rate-limit = 5 Ping response code, default is 204default-ping-response = 200 Enable HTTPS requests.ssl-combined-pem = "/etc/ssl/certs/localhost.crt" [[http.output]] [[http.output]] [[udp]] Precision to use for timestampsprecision = "n" # Can be n, u, ms, s, m, h [[udp.output]] [[udp.output]] EOF |
server2:- influxdb-relay.conf file influxDB && Prometheus[[http]] Timeout for /health routeAfter this time, the host may be considered downhealth-timeout-ms = 10000 Request limiting (Applied to all backend)rate-limit = 5 Ping response code, default is 204default-ping-response = 200 Enable HTTPS requests.ssl-combined-pem = "/etc/ssl/certs/localhost.crt" [[http.output]] [[http.output]] [[udp]] Precision to use for timestampsprecision = "n" # Can be n, u, ms, s, m, h [[udp.output]] [[udp.output]] EOF |
I to also want to know how the relay is writing the data and we are mentioning the connection between the instance and relay and how do we mention the writing data from Prometheus to relay |
how to test influxdb-relay working or not on multinode…?
server1: I install influxdb and influxdb-relay and both running
server2: I install influxdb and influxdb-relay and both running
so what next … I want exact steps to test influxdb-relay working or not
The text was updated successfully, but these errors were encountered: