Option to redirect subscriber tree debug output to file instead of stdout

[Chandrachud28]

Hi,

I wanted to ask if it would be possible to provide an option to redirect the subscriber tree output (triggered via SIGUSR2) to a file, instead of printing directly to stdout.

Currently, when inspecting the subscriber tree (for debugging or analysis), the output is written to the console. While general logging can be redirected using existing configuration options (e.g., log_dest file), this does not seem to apply to subscriber tree output on receiving SIGUSR2.

This creates a few challenges:

• Difficult to capture and analyze output in headless or embedded environments
• No straightforward way to persist or post-process this information

Would it be feasible to support one of the following approaches?

• A configuration option to write subscriber tree output to a file (e.g., under /tmp)
• A command-line flag to redirect this specific debug output
• A build-time option

If there is already a recommended way to capture this output cleanly, I would appreciate any guidance.

Thanks!