Missing Metrics for last machine contact #694

Closed
opened 2025-12-29 02:22:11 +01:00 by adam · 1 comment
Owner

Originally created by @wrenix on GitHub (Apr 18, 2024).

Bug description

after:
https://github.com/juanfont/headscale/pull/1492

several metrics does not exists anymore.

i miss the metrics headscale_last_update_seconds which was nice for alerting if a machine was not connect correct with tailscale.

Environment

  • OS:
  • Headscale version: main
  • Tailscale version: X
  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

To Reproduce

Logs and attachments

Originally created by @wrenix on GitHub (Apr 18, 2024). ## Bug description after: https://github.com/juanfont/headscale/pull/1492 several metrics does not exists anymore. i miss the metrics `headscale_last_update_seconds` which was nice for alerting if a machine was not connect correct with tailscale. ## Environment - OS: - Headscale version: main - Tailscale version: X <!-- We do not support running Headscale in a container nor behind a (reverse) proxy. If either of these are true for your environment, ask the community in Discord instead of filing a bug report. --> - [x] Headscale is behind a (reverse) proxy - [x] Headscale runs in a container ## To Reproduce <!-- Steps to reproduce the behavior. --> ## Logs and attachments <!-- Please attach files with: - Client netmap dump (see below) - ACL configuration - Headscale configuration Dump the netmap of tailscale clients: `tailscale debug netmap > DESCRIPTIVE_NAME.json` Please provide information describing the netmap, which client, which headscale version etc. -->
adam added the bug label 2025-12-29 02:22:11 +01:00
adam closed this issue 2025-12-29 02:22:11 +01:00
Author
Owner

@kradalby commented on GitHub (Apr 21, 2024):

Hi, this metric does not exist anymore due to a change in how we distribute updates. It will not return, but I am redoing the metrics that had been left and you can preview them in https://github.com/juanfont/headscale/pull/1895.

The closest/most relevant for a similar purpose might be:

# HELP headscale_notifier_open_channels_total total count open channels in notifier
# TYPE headscale_notifier_open_channels_total gauge
headscale_notifier_open_channels_total 149

# HELP headscale_mapresponse_current_sessions_total total count open map response sessions
# TYPE headscale_mapresponse_current_sessions_total gauge
headscale_mapresponse_current_sessions_total 150
@kradalby commented on GitHub (Apr 21, 2024): Hi, this metric does not exist anymore due to a change in how we distribute updates. It will not return, but I am redoing the metrics that had been left and you can preview them in https://github.com/juanfont/headscale/pull/1895. The closest/most relevant for a similar purpose might be: ``` # HELP headscale_notifier_open_channels_total total count open channels in notifier # TYPE headscale_notifier_open_channels_total gauge headscale_notifier_open_channels_total 149 # HELP headscale_mapresponse_current_sessions_total total count open map response sessions # TYPE headscale_mapresponse_current_sessions_total gauge headscale_mapresponse_current_sessions_total 150 ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#694