Use “Is this Tailscale diagnostic telling me anything” in Recued. Reads the local node's backend state first, because almost every other tailscale read answers cheerfully whether or not the node is on the tailnet. It reads information without changing data in the connected service.

How it works 13 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (13 steps)

◆ status recued-core.tailscale-cli.node.status

Status node on tailscale cli

■ have_status template

Generate text from a template

fail: step.status.stdout is_null

■ state default

Apply default

■ running compare

Check if state equals Running

■ defaults defaults

Apply defaults

■ health_count count

Count items in health

■ healthy compare

Check if health is empty

■ peers default

Apply default

■ have_peers compare

Check if peers exists

◆ lock recued-core.tailscale-cli.tailnet_lock.status

Status tailnet lock on tailscale cli

■ lock_enabled default

Apply default

■ card to_summary

Format results as a summary card

■ health_table to_table

Format results as a data table

▼

Output

summary card

table health_table