> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Magazine and Audit Magazine

> Where to look for operational events and configuration changes in the panel.

In the side menu there are two different sections.

## Journal of operations

Open **Management → Operations Log**. This is a combination of health incidents and node events.

Use this:

* **All**, **Critical**, **Attention**, **Info**;
* switches **All**, **Incidents**, **Events nod**;
* Text search.

The history of one node is more convenient to see on its page in the tab **Journal**.

## Audit magazine

Open **Management → Audit-magazine**. Here you can see the actions of administrators and the system: who, when and what resource has changed.

Use the search bar and presets. To investigate, start with a short subsystem name, such as `egress`, `backup`, or `eagent`.

## The result of the operation and technical history

The audit shows the explicit events of operations and object changes: who acted, what object was affected, how the action ended, and what fields changed. HTTP method and successful response alone do not prove the creation or modification of the object.

For nodes and groups, the creation, modification, import, deletion, composition change, completion of inspection and installation are separately recorded. A mass operation produces results on objects; maintaining the same values does not create a new change event. Secrets are excluded from the images and the difference.

Old automatic query records remain technical history and are available when technical entries are turned on. They are not confirmation of a completed business action. External SSH operation and local DB record have different boundaries: the lack of a successful result requires checking the actual state of the server.

## What to attach to the appeal

1. On the panel server, run `sudo axottle` and open **Doctor**.
2. Wait for the diagnosis to end and select the log period that covers the onset of the problem.
3. Select **Collect support bundle**, view the archive composition and save it locally or send it from TUI.
4. In the request, indicate the time of the problem with the time zone and the actions already taken, including attempts to safely recover.

Support bundle includes the result of `axottle doctor`, system images and available logs. Secrets in text files are masked automatically. If TUI is not available, attach the output of `axottle doctor` and the desired snippet from `axottle logs` — more details in the [directory CLI](https://docs.axottle.com/en/reference/cli.md).

Both logs are available in the read-only panel; rollback is done in the section where the configuration has changed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.