> ## 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.

# Response to incidents

> Where to watch in case of an incident, the order of action, the collection of support bundle and escalation in support.

When something went wrong -- the node fell, the configuration application broke, the surge of the abuse -- it's important to quickly understand the scale and act in order, not at random. This page is a short map: where to look, what to do and how to escalate.

> [!NOTE]
>
> For whom: panel administrator / SRE / duty engineer. Required rights: administrator session; for support bundle - access to the console of the host panel.

## Where to look.

| Source | What shows | where |
| - | - | - |
| Health-dashboard | Current Flow status and nodes, active health incidents | section **Health** panel |
| Journal | Ribbon of health incidents and node events on one timeline | section **Journal**, see [Journal and audit](https://docs.axottle.com/en/panel/journal-and-audit.md) |
| Incidents of | Abuse Signals and Incidents of | Anti-Abuse System Section **Abuse**, see [AbuseProtect](https://docs.axottle.com/en/abuse/overview.md) |
| Audit Log | Who and what changed (person or system) - for the question "what changed before the incident?" | section **Audit-journal** |
| Notifications | Notifications Telegram Alerts on signed categories | [Notifications](https://docs.axottle.com/en/panel/notifications.md) |

## Procedures for action

**1. Estimate the scale.**

One node, one Flow or the whole panel? Health dashboard gives the answer the fastest. If the panel itself is not available, start with `axottle doctor` on the panel host ([Regular maintenance](https://docs.axottle.com/en/operations/maintenance.md)).

**2. Health diagnostics**

Open the incident on the health dashboard: you can see the affected components and transition history. For typical scenarios, follow the ready-made runbooks: [Runbooks](https://docs.axottle.com/en/health/runbooks.md).

**3. Journal and audit**

In the Journal, look for events around the time the incident started; in the audit log, check if the incident coincided with a configuration change, policy application or update. The question "what changed last?" resolves most incidents.

**4. Act on a runbook.**

Follow the steps of the appropriate runbook. Typical recovery tools: geo-assets rollback, egress block removal, recovery from the backup, re-application of the configuration — each function has a rollback section on its page.

## Escalation

If the incident is not resolved on its own:

**1. Collect a support bundle**

On the panel server, run `sudo axottle`, open **Doctor**, select the log period and collect the support bundle. Before sending, review the archive composition - detailed instructions are available on the [Service page and Axottle Doctor](https://docs.axottle.com/en/operations/maintenance.md#support-bundle).

**2. Describe the incident**

What to write in a ticket - see checklist in [Journal and audit](https://docs.axottle.com/en/panel/journal-and-audit.md#что-приложить-к-обращению) and general order in [Ecalations](https://docs.axottle.com/en/troubleshooting/escalation.md).

**3. Contact support.**

Email in support of Axottle: [@axosupport](https://t.me/axosupport). Attach support bundle and chronology.

## Verification

> [!TIP]
>
> The incident is closed if the health dashboard has returned to a green state, new events on the affected components in the Journal have stopped, and the cause is fixed (in a ticket or an internal note).

## Rollback

This page describes a process, not a change operation - there is nothing to roll back. The rollbacks of specific recovery actions are described on the pages of the corresponding functions (backups, egress, geo-assets, updates).

## Typical errors

> [accordion] Fix the symptom without looking at the audit log
>
> Reboots rarely help if the reason is yesterday's policy change: first, "what changed?", then action.

> [accordion] Escalate without support bundle
>
> Tickets without diagnosis almost always come back with the question "send bundle." Collect the archive immediately - it's minutes.

Related pages: [Runbooks](https://docs.axottle.com/en/health/runbooks.md), [Escalation](https://docs.axottle.com/en/troubleshooting/escalation.md), [Service and Axottle Doctor](https://docs.axottle.com/en/operations/maintenance.md), [Journal and audit](https://docs.axottle.com/en/panel/journal-and-audit.md).


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