-
Notifications
You must be signed in to change notification settings - Fork 78
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
Add info about running Prometheus on a separate host. #291
Conversation
…igners. Signed-off-by: Byron Gravenorst <[email protected]>
Signed-off-by: Byron Gravenorst <[email protected]>
Signed-off-by: Byron Gravenorst <[email protected]>
Signed-off-by: Byron Gravenorst <[email protected]>
…to bgravenorst-TEKU-194
Signed-off-by: bgravenorst <[email protected]>
docs/HowTo/Monitor/Metrics.md
Outdated
!!! important | ||
|
||
If running Prometheus on a different host to your Teku node (any host other than `localhost`), | ||
ensure you add the Prometheus host to [`--metrics-host-allowlist`](../../Reference/CLI/CLI-Syntax.md#metrics-host-allowlist) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not the prometheus host that needs to be added, but the hostname that prometheus uses to connect to Teku.
So if prometheus is configured to get metrics from http://teku.local:8008/metrics
then teku.local
has to be in the metrics host allow list. It doesn't matter what the hostname of the prometheus box is.
Signed-off-by: bgravenorst <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Describe the change
Add info about running Prometheus on a separate host.
Issue fixed
Fixes #290