DumbMonit

IntegraçõesRede e firewalls

Monitorizar Tailscale com o DumbMonit

The devices of a tailnet through the Tailscale API: servers offline, node keys about to expire, devices awaiting approval, clients to update, and each device's last connection.

DocumentaçãoSite oficial: Tailscale

As descrições estão em inglês, como no produto. Os rótulos da página seguem o seu idioma.

O que o DumbMonit vigia

The devices of a tailnet through the Tailscale API: servers that went offline, node keys about to expire, devices waiting for approval, and clients with an update available. DumbMonit reads GET /api/v2/tailnet/{tailnet}/devices on api.tailscale.com, once a minute. The recommended credential is an OAuth client limited to the devices:core:read scope: DumbMonit exchanges its ID and secret for a one-hour token (/api/v2/oauth/token) and keeps it until it expires. It can list the devices and change nothing. An API access token (tskey-api-…) works too, but it carries every right of the user who created it and expires after 90 days at most.

Utilização típica. Tailnet: servers offline, node keys expiring, devices awaiting approval

Exemplos

  • Tailscale tailnet
  • Subnet routers
  • Exit nodes

Como se liga

O que precisa

  • OAuth clientRecommended: a client limited to the devices:core:read scope, which can change nothing.
  • API access tokenWorks too, but carries every right of the user who created it and expires after 90 days at most.

Portas de rede a abrir

  • 443/TCPTailscale API (HTTPS, api.tailscale.com)
Passos de configuração: Create a read-only OAuth client for DumbMonit
  1. In the Tailscale console (login.tailscale.com), open Settings → Trust credentials → Credential → OAuth.

  2. Tick only the read scope listed below, then click Generate credential.

  3. Copy the client ID and the client secret (tskey-client-...): the secret is shown once.

  4. In DumbMonit, enter api.tailscale.com as address and paste them as Client ID and Client secret; leave the Tailnet option empty.

Atenção. Only tagged devices (servers, subnet routers, exit nodes) are expected to stay online: name the ones to watch in the Devices to keep online option, or enter all.