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

# Diagnostics Export

> Download a diagnostics package for troubleshooting and support

A diagnostics package is a zip file containing operational data about your
Thoras deployment. Since Thoras runs self-hosted in your cluster, this is the
primary way to share deployment context with the Thoras team when you need
support or want a configuration review.

It does not include application secrets, credentials, environment variables,
workload application logs, or business data. You can always unzip and inspect it
before sharing.

## What's included

* Cluster info (node types, capacity, availability zones)
* Thoras configuration and workload scaling settings
* Scaling history (suggestions, metrics, resource usage over time)
* Cost and utilization data
* Optionally, Thoras service logs

## Downloading from the dashboard

### Cluster-wide export

From the dashboard homepage, open the **Manage Cluster** dropdown in the header
and select **Download diagnostics**. This exports data for all enrolled
AIScaleTargets.

The dashboard uses a 7-day time range and includes Thoras pod logs by default
(you can uncheck this). Full per-workload metrics are excluded from cluster-wide
exports to keep file size manageable.

### Single-AST export

Navigate to a specific AIScaleTarget page, then open **Manage Cluster** and
select **Download diagnostics**. This exports data for that workload only, with
full metrics included.

To include all ASTs from this page instead, check **Include all AI Scale
Targets** in the export dialog.

## Downloading via API

Port-forward the API server:

```bash theme={null}
kubectl port-forward svc/thoras-api-server-v2 8080:80 -n thoras
```

Then download:

```bash theme={null}
curl -o diagnostics.zip \
  "http://localhost:8080/v1/export?start=2026-10-01T00%3A00%3A00Z&end=2026-10-14T00%3A00%3A00Z&include-pod-logs=true&include-metrics=false"
```

### Query parameters

| Parameter | Type | Required | Default | Description |
| - | - | - | - | - |
| `start` | ISO 8601 timestamp | Yes | -- | Start of the time range |
| `end` | ISO 8601 timestamp | Yes | -- | End of the time range |
| `include-pod-logs` | boolean | No | `false` | Include Thoras service pod logs |
| `include-metrics` | boolean | No | `false` | Include full metrics for the time range. When false, only the last 10 minutes of metrics are included per AST. |
| `namespace` | string | No | all | Filter to a specific namespace |
| `targetName` | string | No | all | Filter to a specific AIScaleTarget name (requires `namespace`) |

### Examples

**Cluster-wide with pod logs:**

```bash theme={null}
curl -o cluster-diagnostics.zip \
  "http://localhost:8080/v1/export?start=2026-10-01T00%3A00%3A00Z&end=2026-10-14T00%3A00%3A00Z&include-pod-logs=true&include-metrics=false"
```

**Single workload with full metrics:**

```bash theme={null}
curl -o workload-diagnostics.zip \
  "http://localhost:8080/v1/export?start=2026-10-01T00%3A00%3A00Z&end=2026-10-14T00%3A00%3A00Z&include-metrics=true&namespace=my-namespace&targetName=my-workload"
```

**All workloads in a namespace:**

```bash theme={null}
curl -o namespace-diagnostics.zip \
  "http://localhost:8080/v1/export?start=2026-10-01T00%3A00%3A00Z&end=2026-10-14T00%3A00%3A00Z&namespace=my-namespace"
```

<Note>
  Full metrics can be large for clusters with many ASTs. For cluster-wide
  exports, consider leaving `include-metrics=false` and only requesting full
  metrics for specific workloads you're investigating.
</Note>

## Sharing with Thoras

Send your diagnostics package to the Thoras team via your shared Slack channel,
email at [support@thoras.ai](mailto:support@thoras.ai), or any file transfer tool your team prefers (e.g.,
[magic-wormhole](https://github.com/magic-wormhole/magic-wormhole)).


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