> For the complete documentation index, see [llms.txt](https://brightercommand.gitbook.io/paramore-brighter-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brightercommand.gitbook.io/paramore-brighter-documentation/health-checks-and-observability.md).

# Health Checks and Observability

- [Logging](https://brightercommand.gitbook.io/paramore-brighter-documentation/health-checks-and-observability/logging.md): Brighter writes its diagnostics through Microsoft.Extensions.Logging, and takes its ILoggerFactory from a single static holder rather than from your container.
- [Monitoring](https://brightercommand.gitbook.io/paramore-brighter-documentation/health-checks-and-observability/monitoring.md): A monitored handler posts an event to a control bus as it is entered and exited, so you can watch what your handlers do from outside the process.
- [Health Checks](https://brightercommand.gitbook.io/paramore-brighter-documentation/health-checks-and-observability/healthchecks.md): Brighter provides ASP.NET Core health checks that report whether the Dispatcher's consumers are running and reading their channels.
- [Telemetry](https://brightercommand.gitbook.io/paramore-brighter-documentation/health-checks-and-observability/telemetry.md): Brighter provides comprehensive OpenTelemetry integration for distributed tracing across message boundaries, enabling end-to-end observability in distributed systems.
- [Configuring OpenTelemetry](https://brightercommand.gitbook.io/paramore-brighter-documentation/health-checks-and-observability/telemetry/configuringopentelemetry.md): The OpenTelemetry SDK can be configured to listen to Activities emitted by Brighter.


---

# 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://brightercommand.gitbook.io/paramore-brighter-documentation/health-checks-and-observability.md?ask=<question>&goal=<user_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.