Authelia Telemety Settings / Grafana / Prometheus

[TroRon]

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.
But I can't get the Prometheus / Authelia connection to work.

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?

Authelia Log:

Testing:

Everything runs on the same machine

[glime-ai[bot]]

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:

1. Verify Authelia Configuration: Ensure that the telemetry configuration in Authelia is correctly set to enable the Prometheus metrics exporter. The configuration should look something like this:

   telemetry:
     metrics:
       enabled: true
       address: 'tcp://:9959/'

   Make sure that enabled is set to true and the address is correctly formatted.

2. Check Docker Network Settings: Since both Prometheus and Authelia are running inside Docker, ensure that they are on the same Docker network or can communicate over the network. You might need to check the network settings in your Docker Compose or Docker command.

3. Inspect Authelia Logs: Look at the Authelia container logs to see if there are any errors or warnings related to the metrics server starting up or listening on the port. This can give you clues about what might be going wrong.

4. Test Network Accessibility: From within the Prometheus container, try to telnet or curl the Authelia metrics endpoint:

   curl http://authelia:9959/metrics

   This can help verify network connectivity between the Prometheus and Authelia containers.

5. Review Prometheus Configuration: Ensure that your Prometheus configuration is set up to scrape metrics from Authelia. The job configuration in Prometheus should look something like this:

   - job_name: 'authelia'
     static_configs:
       - targets: ['authelia:9959']

   Replace 'authelia:9959' with the appropriate address if Authelia is reachable via a different hostname or IP in your setup.

6. Check for Port Conflicts: Even though you mentioned the firewall is not an issue, ensure there are no other services running inside or outside Docker that might be using port 9959.

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.

[james-d-elliott]

You've not published the port in docker.

[james-d-elliott]

Yeah you need to publish the port per standard docker semantics for the iptables rules to be created to translate the port.

[james-d-elliott]

docker exec authelia wget -O - http://127.0.0.1:9959/metrics

[TroRon]

authelia:
restart: unless-stopped
image: authelia/authelia
container_name: authelia_server
volumes:
- /docker/authelia:/config
ports:
- 19091:9091
- 9959:9959
environment:
- TZ=Europe/Zurich

[TroRon]

URL without /metrics works now:

[TroRon]

Solved, add /metrics in the Authelia Config ;)

[TroRon]

A little bit is already displayed ;)