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
Scraping multiple endpoints not clear using multiple piholes. #116
Comments
i went looking for this info as well, but i am running via cli/systemd, sharing for others benefit
use a comma to separate the ip's/hostnames, and then also a comma to separate api token |
Do you expose then one (i.e. |
I'm not using docker, I built from source and run the app via systemd and use one instance to connect to two piholes. In Prometheus I only have one data source configured, so I expect the same logic would apply for docker, i.e. just 9617 |
Exactly, that was the point I want to clarify. If you have configured just one data source, how looks like the aggregation for the metrics ( Example with just one port and hostname:
Thanks. |
it looks exactly like your example, the hostname is included which is how grafana then separates it. you get two sets of results, one for each hostname/ip:
|
Asumming that:
How I query the metrics behind for the three piholes
192.168.178.70, 192.168.178.80, 192.168.178.120
?I just know
curl 192.168.178.70:9617/metrics
what is performed by prometheus but doing that I'm just getting the first host metrics certainly.Using
linux amd64
.The text was updated successfully, but these errors were encountered: