> For the complete documentation index, see [llms.txt](https://docs.flopsar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flopsar.com/7/user-guide/opentelemetry.md).

# OpenTelemetry

Flopsar can ingest [OpenTelemetry](https://opentelemetry.io/) **traces** over OTLP and store them next to native JVM data from Flopsar agents. Configure the receivers in `[otlp]` — see the [Server Configuration Reference](/7/administrator-guide/configuration/server-configuration-reference.md) and [Server](/7/administrator-guide/server.md#opentelemetry). A license that includes OpenTelemetry is required.

The server accepts OTLP traces only (not metrics or logs). Default bind ports are **4318** (HTTP) and **4317** (gRPC).

{% hint style="info" %}
**Screenshot placeholder:** OpenTelemetry Data Browser — trace list with Time, Application, Name, Subsystems, Spans, and Duration. (The OpenTelemetry sidebar section may be hidden depending on license and build; traces are still ingested when `[otlp]` is enabled.)
{% endhint %}

Explore ingested traces with a data browser, trace details (including the span tree), and analysis comparable to native [Data Analysis](/7/user-guide/observing-and-diagnosing/data-analysis.md).

## Data Browser

Search requires a time range. You can further narrow by [service](https://opentelemetry.io/docs/specs/semconv/attributes-registry/service/) and span [name](https://opentelemetry.io/docs/specs/semconv/rpc/rpc-spans/#service-name). Results list matching traces with:

* **Time** — start of the trace
* **Application** — service name
* **Name** — span name
* **Subsystems** — distinct services in the trace
* **Spans** — call count in the trace
* **Duration** — trace duration

Expanding a trace lists its subsystems (application, span count, exceptions, duration). The sum of subsystem durations need not equal the trace duration.

## Trace Details

Opening a trace shows details (including the subsystems table) and an **Execution Stack** tab with the full span tree. Depending on the span, the Info column may show exception details, events, attributes, and resource information.

## Data Analysis

Analysis uses the same time range and optional service/name filters. The duration-distribution view matches the one for native JVM invocations — see [Data Analysis](/7/user-guide/observing-and-diagnosing/data-analysis.md).