Authelia Telemety Settings / Grafana / Prometheus #7315
-
I am currently working on the telemetry section within the Authelia configuration. I actually want to get the Grafana Dashboard (see Examples) to work. Grafana / Prometheus are running inside Docker. That works. According to the config I added the telemetry block, Authelia also says that it listens on port 9959. But when I check the port it is not open. Firewall is definitely not. Do any of you have this setup running and any idea what else it could be? Everything runs on the same machine |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 9 replies
-
Please note this response was created using generative AI leveraging previously available information from the repository. This information may be helpful however it is our strong recommendation that you carefully consider the information before blindly applying it. To troubleshoot the issue with Prometheus not being able to connect to Authelia on port 9959, even though Authelia is configured to listen on this port, you can follow these steps:
If after these steps the issue persists, it might be helpful to provide more specific logs or error messages from both the Authelia and Prometheus containers to further diagnose the problem. This comment was generated by Glime. |
Beta Was this translation helpful? Give feedback.
-
You've not published the port in docker. |
Beta Was this translation helpful? Give feedback.
-
A little bit is already displayed ;) |
Beta Was this translation helpful? Give feedback.
-
Thank you for this topic. Per the example configuration (included on this page: https://www.authelia.com/configuration/telemetry/metrics/), the address is:
However, doing this will just lead to 404 in Prometheus. It needs to be:
This works without any need to expose 9959. Can we get that example config changed, please? |
Beta Was this translation helpful? Give feedback.
You've not published the port in docker.