Log
Read short troubleshooting logs after one clean reproduction.
Use Log for short troubleshooting sessions. Choose a severity level, clear old entries, reproduce the problem once, then read the newest entries first. Tunna shows the newest 50 recent log rows, newest first.
Log controls
Use these cards as a map of the visible labels in this view. Each card names one field, control, or status item and explains what it is for before you change it or rely on it.
Visible choices
These are controls, states, or measurements in the view. Read them as reference, not as feature claims.
Severity
Segmented picker: None, Error, Warning, Info, or Debug. Higher levels include lower levels. Use Debug only while reproducing a problem, then lower it again.
Access
Adds connection-level traffic behavior. Access entries appear as Info.
DNS
Adds name-resolution behavior. DNS entries appear as Debug, so use Debug when you need to see them in the normal list.
Search
Search matches message text and severity names, case-insensitively. Search looks through stored logs even when the severity picker is set lower.
Clear
Clears saved log entries before a fresh test. It clears stored and in-memory entries, not just the visible filtered rows.
Rows
Each row shows a colored dot, uppercase severity, timestamp, and monospaced message. Gray is None, red Error, yellow Warning, green Info, and blue Debug.
Use Log after Observability shows a problem
Observability tells you that latency is high, probing is still in progress, or recent checks timed out. Log tells you what Tunna recorded during a reproduction. Clear logs, run one focused test, then compare the newest messages with the node latency state.
Log controls save as you change them
Severity, Access, and DNS are stored when the log configuration changes. Search is temporary, and Clear removes stored and in-memory log entries. No Logs Found means the current filter or stored history has no matching rows.
Debug is temporary
Debug, Access, and DNS logs are useful for diagnosis, but they can increase battery, CPU, memory, storage, data use, and noise. Turn them back down after the test.