Show more insights of the underlying oxidized process

Open robertcheramy opened this issue 6 months ago • 1 comments

When looking into a Problem in oxidized, the possibilities to check what is going on are limited.

As an example, the aos_apc model seems to block my oxidized instance, but I have no Idea why yet. The new logging possibilities in oxidized could help here, but sending SIGUSR2 or SIGTTIN on the CLI is not very user friendly.

It would be great to provide possibilities to look into what is going on in the web interface:

Configured log level (read/write)
See the last logs
See which Nodes are in the queue and which are being processed

The access to these Features should (optionnaly) be restricted to authenticated user groups (admins).

Jul 09 '25 05:07 robertcheramy

This issue is stale because it has been open 90 days with no activity.

Oct 08 '25 02:10 github-actions[bot]