Capture a focused Tvheadend subsystem debug window

The useful distinctions

• Configuration, Debugging exposes debug log path and subsystem controls.
• Those web-interface settings apply to the current runtime rather than being saved persistently.
• Trace output requires a build compiled with trace debugging support.

Choose the subsystem from the action

A recording that fails at a repeatable step is a more useful starting point than a general request for maximum logging. Write down that step and the expected result, then choose the subsystem relevant to it. For a recording-management action, the documented DVR subsystem gives the capture a clear focus. An unrelated trace category can generate volume without answering the specific question.

Keep runtime and startup choices separate

The web controls provide a temporary diagnostic setting for the running process. Record that context with the capture so someone does not assume the same configuration will still apply after a restart. The synthetic plan uses a dedicated filename and a short reproduction. It does not ask you to start another server instance, force a crash or alter the operating system’s core-dump behavior.

Finish with a useful report

Stop the experiment after the intended event and preserve only the interval needed to describe it. Review the log before sharing because diagnostic details can reveal local paths or server context. If trace detail is requested but absent, check the build capability instead of assuming that an empty trace proves the subsystem did no work. Include the installed version, selected categories and exact action so a maintainer can interpret the evidence.

A focused way to proceed

1. Record the relevant action and existing debug settings.
2. As administrator, open Configuration and Debugging.
3. Choose an appropriate subsystem such as dvr and a new log destination.
4. Reproduce the action once, preserve its log window and return the runtime controls to their earlier state.

Worked example · synthetic

Debug subsystem: dvr
Log destination: workshop-dvr-debug.log
Window: one authorized test recording action
After capture: restore earlier runtime controls
Trace: request only if the installed build supports it

Read the comparison

A missing trace may reflect the build configuration; runtime debug changes are not a persistent service policy.

When to stop or ask for help

Provide the reviewed capture, build information and precise action to Tvheadend support.