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

# Escalation

> When and how to escalate: collecting a support bundle with masking secrets, the composition of the treatment and private disclosure of vulnerabilities.

If the typical diagnostics didn't work, it's time to escalate -- but in a way that gives support enough context and no secret leaves your environment, and this page shows you what to collect, what to apply, and where to turn.

> [!NOTE]
>
> For whom: panel administrator, SRE, security specialist. Rights required: access to the panel host console (for `axottle doctor`) and to the audit log.

## When escalate

Escalate when:

* passed [general procedure for diagnosis](https://docs.axottle.com/en/troubleshooting/common-problems.md) and profile page section, but the reason was not found;
* the problem is reproduced and affects users (`critical` nodes, schemas are not applied, the gateway is not available);
* You suspect a defect in the product itself, not a configuration error.
* If you find a vulnerability, then go directly to the [Vulnerability Disclosure](#раскрытие-уязвимостей) section below, bypassing the usual ticket.

Before you write an appeal, collect a diagnosis - with it the answer will come faster.

## Collect a support bundle

**Support bundle** is a diagnostic archive that helps support to see the status of the server and events around the failure.

**1. Open the Doctor.**

On the panel server, run the interactive menu:

```bash theme={null}
sudo axottle
```

Select **Doctor** and wait until the check is completed.

**2. Select the period of journals**

In the **Log period**, select a period that begins a little earlier than the first signs of a problem. 6 hours is usually appropriate for a two-hour-old failure.

**3. Collect an archive.**

Select **Collect support bundle** and wait for the collection to end. Passwords, keys and tokens are masked before saving.

**4. Check and send.**

Select **Save bundle locally**, open `manifest.json` inside the archive and check the source list. Then go back to **Send bundle to support** and submit the archive. If the download failed, attach the saved file to manually access.

> [!WARNING]
>
> Before sending an archive outside the organization, review its composition and make sure that non-standard logs do not contain sensitive data specific to your environment.

## What to put in the ticket

The more specific the treatment, the faster the analysis.

| What is | Where to get a | |
| - | - | - |
| Version of the panel and agents | `axottle version`, tab **Agent** on the nodes | |
| The exact symptom and steps of | playback is your observation; if possible, the HTTP status of the | response |
| Affected nodes/circuits | ID and node names and Flow | |
| The time interval of the | incident when | was spotted |
| Extracts from | [Journal and audit](https://docs.axottle.com/en/panel/journal-and-audit.md) - **without secrets** | |
| Support bundle | `sudo axottle` → **Doctor** (see above) | |

> [!WARNING]
>
> Do not attach real secrets, tokens, keys, full subscription URLs and internal addresses. Use placeholders (`panel.example.com`, `203.0.113.10`, `axt_xxxxxxxx…`). Log extracts are manually cleared of secrets - automatic masking is guaranteed only for support bundle.

## Contact support

Appeals in support are accepted in Telegram.

> [!NOTE]
>
> Support contact: [@axosupport](https://t.me/axosupport).

## Disclosure of Vulnerabilities

Vulnerabilities are a separate, private channel. **Ne** start a public ticket and do not disclose details until the patch is released.

* Notify private contact for responsible disclosure.
* In the appeal, specify: the affected version, description, reproduction steps and potential impact - with impersonal examples, without real secrets.
* Full order - [- Management of vulnerabilities](https://docs.axottle.com/en/security/vulnerability-management.md).

## Checklist before escalation

* [ ] Passed [Type problems](https://docs.axottle.com/en/troubleshooting/common-problems.md) and profile section diagnostics page.
* [ ] Service tested and `axottle doctor` disassembled by `Failed`/`Warning`.
* [ ] Operations Log and [Z Audit Journal ](https://docs.axottle.com/en/panel/journal-and-audit.md) for the period of the incident are viewed.
* [ ] Collected support bundle, viewed his manifesto.
* [ ] Prepared version, symptom, affected nodes, time interval.
* [ ] Secrets have been removed from manual log extracts.
* [ ] If it is a vulnerability, a private channel is chosen, not a regular ticket.

## Related pages

> [card] [Typical problems](https://docs.axottle.com/en/troubleshooting/common-problems.md)
>
> Symptoms, reasons for where to go.

> [card] [Response to incidents](https://docs.axottle.com/en/operations/incident-response.md)
>
> Scenario of action in the incident.

> [card] [Service](https://docs.axottle.com/en/operations/maintenance.md)
>
> Doctor and support bundle details.

> [card] [Vulnerability management](https://docs.axottle.com/en/security/vulnerability-management.md)
>
> Private disclosure of vulnerabilities.


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