-
Notifications
You must be signed in to change notification settings - Fork 211
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement an initial version of the support bundle in Alloy (#2009)
* Implement an initial version of the support bundle in Alloy * Add documentation for support bundle * Update changelog * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * Initial PR feedback * Rewrite http service to use logging library internal to alloy * Revert accidental commit of e2e test changes * Fix comment on exported function * Clean up added host variable that is no longer used * Refactor usage of logger in http service * Update internal/service/http/http.go Co-authored-by: Piotr <[email protected]> * implement PR feedback * Hide support bundle behind public preview stability level * Update docs based on feedback * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/support_bundle.md Co-authored-by: Clayton Cornell <[email protected]> * More PR feedback in docs * Fix race condition in logger * Add a note about backward-compatibility exception --------- Co-authored-by: Clayton Cornell <[email protected]> Co-authored-by: Piotr <[email protected]>
- Loading branch information
1 parent
bc50984
commit e894439
Showing
10 changed files
with
445 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
--- | ||
canonical: https://grafana.com/docs/alloy/latest/troubleshoot/support_bundle/ | ||
description: Learn how to generate a support bundle | ||
title: Generate a support bundle | ||
menuTitle: Generate a support bundle | ||
weight: 300 | ||
--- | ||
|
||
<span class="badge docs-labels__stage docs-labels__item">Public preview</span> | ||
|
||
# Generate a support bundle | ||
|
||
{{< docs/public-preview product="Generate support bundle" >}} | ||
|
||
The `/-/support?duration=N` endpoint returns a support bundle, a zip file that contains information | ||
about a running {{< param "PRODUCT_NAME" >}} instance, and can be used as a baseline of information when trying | ||
to debug an issue. | ||
|
||
This feature is not covered by our [backward-compatibility][backward-compatibility] guarantees. | ||
|
||
{{< admonition type="note" >}} | ||
This endpoint is enabled by default, but may be disabled using the `--disable-support-bundle` runtime flag. | ||
{{< /admonition >}} | ||
|
||
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 {{< param "PRODUCT_NAME" >}} 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 [supportbundle implementation](https://github.com/grafana/alloy/tree/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][components] running on this {{< param "PRODUCT_NAME" >}} instance, generated by the | ||
`/api/v0/web/components` endpoint. | ||
* `alloy-logs.txt` contains the logs during the bundle generation. | ||
* `alloy-metadata.yaml` contains the {{< param "PRODUCT_NAME" >}} build version and the installation's operating system, architecture, and uptime. | ||
* `alloy-metrics.txt` contains a snapshot of the internal metrics for {{< param "PRODUCT_NAME" >}}. | ||
* `alloy-peers.json` contains information about the identified cluster peers of this {{< param "PRODUCT_NAME" >}} instance, generated by the | ||
`/api/v0/web/peers` endpoint. | ||
* `alloy-runtime-flags.txt` contains the values of the runtime flags available in {{< param "PRODUCT_NAME" >}}. | ||
* 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. | ||
|
||
[profile]: ../profile | ||
[components]: ../../get-started/components/ | ||
[alloy-repo]: https://github.com/grafana/alloy/issues | ||
[backward-compatibility]: ../../introduction/backward-compatibility |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.