---
title: "Generate a support bundle | Grafana Alloy documentation"
description: "Learn how to generate a support bundle"
---

# Generate a support bundle

> Note
> 
> Generate support bundle isn’t available on Alloy v1.4 and older.

The `/-/support?duration=N` endpoint returns a support bundle, a compressed file that contains information about a running Alloy instance, and can be used as a baseline of information when trying to debug an [issue](https://github.com/grafana/alloy/issues/).

This feature isn’t covered by the [backward-compatibility](../../introduction/backward-compatibility/) guarantees.

> Note
> 
> This endpoint is enabled by default, but may be disabled using the `--disable-support-bundle` runtime flag.

The duration parameter is optional, must be less than or equal to the configured HTTP server write timeout, and if not provided, defaults to it. The endpoint is only exposed to the Alloy HTTP server listen address, which defaults to `localhost:12345`.

The support bundle contains all information in plain text, so you can inspect it before sharing to verify that no sensitive information has leaked.

In addition, you can inspect the [support bundle implementation](https://github.com/grafana/alloy/blob/main/internal/service/http/supportbundle.go) to verify the code used to generate these bundles.

A support bundle contains the following data:

- `alloy-components.json` contains information about the [components](../../get-started/components/) running on this Alloy instance, generated by the `/api/v0/web/components` endpoint.
- `alloy-environment.txt` contains the values of several environment variables relevant to the golang runtime.
- `alloy-logs.txt` contains the logs during the bundle generation.
- `alloy-metadata.yaml` contains the Alloy build version and the installation’s operating system, architecture, and uptime.
- `alloy-metrics-sample-start.txt` contains a snapshot of the internal metrics for Alloy at the start of the bundle collection.
- `alloy-metrics-sample-end.txt` contains a snapshot of the internal metrics for Alloy at the end of the bundle collection.
- `alloy-peers.json` contains information about the identified cluster peers of this Alloy instance, generated by the `/api/v0/web/peers` endpoint.
- `alloy-runtime-flags.txt` contains the values of the runtime flags available in Alloy.
- The `pprof/` directory contains Go runtime profiling data (CPU, heap, goroutine, mutex, block profiles) as exported by the pprof package. Refer to the [profile](../profile/) documentation for more details on how to use this information.
- The `sources/` directory contains copies of the local configuration files used to configure Alloy.
- `sources/remote-config/remote.alloy` contains a copy of the last received [remote configuration](../../reference/config-blocks/remotecfg/).