# OpenTelemetry (/docs/ai/components/open-telemetry)



## Component category [#component-category]

Telemetry and instrumentation

## Component description [#component-description]

OpenTelemetry is the standard instrumentation and transport layer used by BullSequana AI services to emit traces, metrics, and logs in a consistent way.

## Why it is used [#why-it-is-used]

It connects application activity to the shared Foundation observability stack. In 1.3.0, the BSQAI API and MCP Gateway export application telemetry to the Alloy gateway. Tempo also sends its own operational telemetry to Alloy.

Alloy sends traces to Tempo, metrics to Prometheus, and OTLP logs to Loki under the `platform` tenant. KServe metrics are collected separately through Prometheus scraping; KServe workloads are not configured as general OTLP trace or log emitters.

GenAI-specific workflow spans also use an isolated OpenTelemetry provider to reach MLflow without replacing the platform-wide exporter.

## Learn more [#learn-more]

* [OpenTelemetry Documentation](https://opentelemetry.io/docs/)
* [OpenTelemetry on GitHub](https://github.com/open-telemetry)

## Interacts with [#interacts-with]

* `BSQAI API` and `MCP Gateway` as instrumented application services
* `MLflow` as the separate destination for GenAI observability traces
* Foundation observability services such as `Grafana Alloy`, `Tempo`, and `Prometheus`