> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/integrations/extensions.md).
# Extensions
Add capability to the Bindplane Collector with OTel extensions
#### What are Extensions?
Extensions are components in a Configuration that add capabilities to the Collector. They use OpenTelemetry extensions under the hood. A common use case for extensions could be to configure\
a local server to return the Collector's healthy status.
#### Managing Extensions
Extensions are configured on a per Configuration basis. To view, edit, or modify extensions for a Configuration, select the Advanced Configuration icon on the bottom right-hand side of the Topology Graph on any Configuration detail page. From the opened menu select "Manage Extensions" and the Extension Editor will be brought up.
#### Extensions Available for Bindplane
| Extension | Description |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ |
| [Custom](/integrations/extensions/custom.md) | Configure any supported OpenTelemetry extension by name |
| [File Storage](/integrations/extensions/file-storage.md) | Persist queue and stateful-processor data to disk so it survives collector restarts |
| [Go Performance Profiler](/integrations/extensions/go-performance-profiler.md) | Expose a Go pprof profiling endpoint for debugging collector CPU and memory behavior |
| [Health Check](/integrations/extensions/health-check.md) | Expose an HTTP endpoint that reports the collector's health status |
| [Redis Storage](/integrations/extensions/redis-storage.md) | Persist queue and stateful-processor data to Redis so it survives collector restarts |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.bindplane.com/integrations/extensions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
