> For the complete documentation index, see [llms.txt](https://docs.ecotone.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecotone.tech/modules/opentelemetry-tracing-and-metrics.md). # OpenTelemetry (Tracing and Metrics) OpenTelemetry integration for tracing and metrics in Ecotone PHP

[**OpenTelemetry**](https://opentelemetry.io/docs/instrumentation/php/) is tracing abstraction to collect and aggregate data such as metrics and traces.\ As OpenTelemetry is tracing abstraction it does not force to use specific Tracing 3rd party. Depending on the needs and preferences, we may choose provides like [DataDog](https://www.datadoghq.com/), [Jaeger](https://www.jaegertracing.io/), [Zipkin](https://zipkin.io/) etc. **Ecotone** brings full tracing using **OpenTelemetry** to your PHP applications. It will provide details about your Message flows no matter if they are synchronous or asynchronous. ## Materials ### Demo implementation * [Demo implementation with Symfony and Laravel](https://github.com/ecotoneframework/php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone) ### Links * [How OpenTelemetry can be used with Ecotone](https://blog.ecotone.tech/tracing-using-opentelemetry/) --- # 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.ecotone.tech/modules/opentelemetry-tracing-and-metrics.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.