Observability
Tune health checks, probe timing, and node health data.
Updated
Observability is the Settings page that checks nodes in the background so Tunna can show fresh latency before you pick one. It keeps recent latency information available for node sorting, ZAP, subscription visibility, and the connection accessory. It is separate from Log: Observability measures node health, while Log records troubleshooting messages.
A probe is a small test trip
A probe is Tunna asking one node to reach a small test address and timing the answer. If the answer comes back quickly, the node looks healthy. If it is slow, fails, or times out, Tunna keeps that result so node lists, Active, Top 10, and ZAP have something real to work from.
Checks make choices better
Health-check tuning
These controls change how often Tunna sends those small test trips and how patient it should be while waiting.
What Tunna tests
Start here when latency never appears or every node looks unavailable.
Enabled
Turns probes on or off. Default is On. Turn it off when you want Tunna to stop running health checks; latency, Active, Top 10, and ZAP may become stale.
Target
The tiny web address each node tries to reach. Default is https://tunna.app/connectivitycheck. Invalid entries fall back to http://gstatic.com/generate_204.
Timeout
How long Tunna waits before calling one probe a failure, from 1 to 30 seconds. Default is 3 seconds. A longer timeout is more patient on slow networks.
How often Tunna tests
More frequent checks make fresher latency numbers and use more battery and data.
Interval
How often active probes repeat, from 3 to 60 seconds. Default is 5 seconds.
Idle Interval
How often probes repeat when Tunna is idle, from 60 to 600 seconds. Default is 120 seconds.
Backoff Interval Limit
How far Tunna may slow down repeated probes when conditions are poor, from 60 to 600 seconds. Default is 300 seconds.
How many Tunna tests at once
Concurrency controls how many nodes can be checked at the same time.
Concurrency
How many nodes Tunna tests at the same time. The slider runs from 1 to 100; default is 30. More is faster for big lists, but it can use more battery and data.
The app groups these controls as Performance, Timing, and Advanced Lifecycle
Performance contains the Concurrency slider. Timing contains Timeout, Interval, and Idle Interval sliders. Advanced Lifecycle contains Backoff Interval Limit. Enabled and Target sit above those sections because they decide whether probes run and where they go.
What the numbers mean
Latency
Latency is the wait time for the test trip. Smaller usually feels better. Green means quick, yellow and orange mean slower, red means failed or timed out.
Probing and Timeout
Probing means Tunna is still collecting enough samples. Timeout means the latest checks did not get useful answers.
Round Trip Time
The stats chart groups recent checks by Hour, Day, Month, or Year and shows average, high, low, middle, and slow-tail results.
Data Usage
Usage shows how much data the selected node sent and received, plus the transfer rate over the selected time range.
Observability colors are measurements; Log colors are messages
Latency colors summarize probe outcomes: green is quick, yellow and orange are slower, and red means failed or timed out. Log colors summarize message severity: gray None, red Error, yellow Warning, green Info, and blue Debug. Use Observability for health trends, then use Log when you need the text behind a failed test.
More checks use more resources
Health checks are tiny, but they are still network trips. Short intervals, high concurrency, and low backoff make Tunna check more often. That can make latency fresher, but it can also use more battery, CPU, and mobile data.
Observability saves when you leave
There is no separate Save button. Tunna keeps the current Enabled, Target, Concurrency, Timeout, Interval, Idle Interval, and Backoff Limit choices when you leave this screen.