# Support bundle

> Create a cleaned-up ZIP file of recent logs, runtime details and configuration fingerprints to send to Proxus support.

Source: https://proxus.io/docs/administer/support-bundle

At the end of this guide, you have a ZIP file that Proxus support can use to analyse a problem. Proxus removes
passwords, tokens, connection strings and file paths from it before you download it.

## Before you start

- A user whose role may open **Platform > System Logs**.
- The time the problem happened, so you can choose a time range that covers it.

## Create the bundle

1. Go to **Platform > System Logs**.
2. Select **Support Bundle** in the toolbar.
3. Set the options and select **Generate**. The browser downloads the file.

*Screenshot: The Generate Support Bundle dialog with the time range, the Include File Logs option and the Generate button marked*

1. **Time Range (hours)**: how far back the logs go, from 1 to 168 hours (one week). The default is 24.
2. **Include File Logs** and **Include Operational Logs**: the log files from disk and the entries of the
   **System Logs** list. Both are ticked by default. **Max Log Files** (1 to 25, default 8) and **Max KB Per File**
   (64 to 4096, default 512) limit how much of the log files goes in; the newest part of each file is kept.
3. **Generate** builds the file and downloads it.

The file is named `proxus-support-bundle-` followed by the date and time in UTC, for example
`proxus-support-bundle-20261015-142233.zip`.

## What is in the bundle

| File | Contents |
| --- | --- |
| `manifest.json` | The options you chose. |
| `runtime-health.json` | The machine name, the operating system and runtime version, the Proxus version, culture and time zone. |
| `config-fingerprint.json` | A few settings in plain text (telemetry database, log level and log options, culture) and a fingerprint of all other settings, so support can see whether the configuration changed without seeing it. |
| `file-logs/` | The end of each log file, cleaned up. |
| `operational-logs.json` | Up to 500 entries of the **System Logs** list. |

Before anything goes into the bundle, Proxus replaces passwords, secrets, API keys, tokens, connection strings,
credentials in addresses and absolute file paths with `[redacted]` or `[path]`. Measured values from your machines
are not included.

> **Note:**
The machine name of the hub is included as it is. Open the ZIP file and check it before you send it if your
company's rules require that.

## Send the bundle

Send the ZIP file to your Proxus partner, or to Proxus support through the [contact form](/contact). Say when the
problem started and what you saw, so support can find it in the logs.

## What's next

- [System logs](https://proxus.io/docs/administer/system-logs)
- [Troubleshoot](https://proxus.io/docs/troubleshoot)