Enable Tailscale client metrics
Now you can expose and collect Tailscale client metrics for use with monitoring systems such as Prometheus for your Tailscale network.
These metrics provide insights into client behavior, health, and performance. For example, you can view information about client connectivity to subnet routers configured in your tailnet.
This enable also the option to monitor tailscale from grafana dashboards
How we can enable this option from add-on config?
Sources: https://tailscale.com/kb/1482/client-metrics
Oh man they keep adding options huh?
I'm at the point that I'm thinking about just not adding more options. It really kills the ease of use and becoming a monster of things.
I would recommend to create a feature request upstream with tailscale, to ask if they can extend an WebUI that provides options like these.
@xeberth It's already part of the web UI, but there is a bug in Tailscale web server, when the --readonly flag is used, ie. tailscale web --readonly is used (as the add-on starts the web ui), tailscale forgets to start up the 5252 port listener for the metrics data on the tailnet IP of the client.
$ /opt/tailscale web
2025/02/21 23:54:16 starting tailscaled web client at http://100.x.x.x:5252
2025/02/21 23:54:16 web server running on: http://localhost:8088
$ /opt/tailscale web --readonly
2025/02/21 23:54:23 web server running on: http://localhost:8088
curl 100.x.x.x:5252/metrics should work with --readonly also
Please open an issue at the tailscale repo with the above information.
Created the TS issue: https://github.com/tailscale/tailscale/issues/15108
The --readonly bug is confirmed upstream, this issue can be closed now.
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!