Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upNetdata Instance naming #4204
Comments
This comment has been minimized.
This comment has been minimized.
|
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided. |
brian-brazil
closed this
May 30, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Mesmer88 commentedMay 30, 2018
I'm trying to integrate multiple Netdata servers with Prometheus and then Grafana.
Problem is that Prometheus sees Netdata targets as IP:port This makes it quite dificult to use variables in Grafana to select the server: trying to use hostname and not IP.
Is there any way to change how Prometheus defines the instance?
Noticed there was a similar issue for Kubernetes.