You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 24, 2021. It is now read-only.
(rephrasing as the previous question was unclear).
Use case: to reuse noderig metrics through Prometheus without cutting the noderig -> beamium -> Warp10 workflow that comes preinstalled on OVH servers.
OVH's Beamium can access noderig HTTP server through the 127.0.0.1 loopback (default on OVH bare metal servers).
Own's Prometheus can access noderig HTTP server through the 192.168.0.1 interface,
I don't want to open noderig to 0.0.0.0 which would need some nftables protection to avoid exposing noderig to the outside world.
My questions are
1/ can noderig be accessed by 2 independent clients or will this mess with the metrics collection
2/ if noderig can be accessed by 2 independent clients, is there a way to have noderig listen to multiple interfaces/ports or should noderig been launched twice ? ./noderig --listen 127.0.0.1:9001 --listen 192.168.0.1:9001
3/ are multiple noderig on a single server a viable setup or is it going to mess something (eg both instance try to store metrics at the same place)