> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/home/observability/tracing-service/overview/trace-formats.md).

# Trace Formats

Tracing Service supports distributed trace ingestion using the OpenTelemetry Protocol (OTLP). OTLP is a vendor-neutral format used by OpenTelemetry SDKs, agents, and collectors to export telemetry data.

{% hint style="info" %}
**Note:** Tracing Service documentation focuses on OTLP trace ingestion. [Metrics](/cloud/home/observability/monitoring-service/overview.md) and [logs](/cloud/home/observability/logging-service/overview.md) use separate observability products and ingestion models.
{% endhint %}

## Supported trace formats

Tracing Service currently accepts traces through the following OTLP transport formats:

| **Protocol** | **Endpoint**                                     | **Note**               |
| ------------ | ------------------------------------------------ | ---------------------- |
| OTLP/HTTP    | `https://<tracing-ingestion-endpoint>/v1/traces` | Sends traces over HTTP |
| OTLP/gRPC    | `grpcs://<tracing-ingestion-endpoint>/v1/traces` | Sends traces over gRPC |

## Trace payload contents

A trace payload can include the following common data structures:

* **Traces:** A logical end-to-end request or workflow.
* **Spans:** Individual operations within a trace.
* **Resource attributes:** Metadata describing the service or workload that emitted the spans, such as `service.name`.
* **Span attributes:** Key-value metadata attached to a span.
* **Events:** Timestamped annotations for notable events during span execution.
* **Links:** Relationships between spans that are not direct parent-child connections.
* **Status:** Success or error information attached to a span.


---

# 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.ionos.com/cloud/home/observability/tracing-service/overview/trace-formats.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.