> 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/api-reference/observability/tracing-service/overview.md).

# Overview

The IONOS CLOUD Tracing API collects OpenTelemetry Protocol (OTLP) traces from any compatible source. It routes them through tenant-isolated pipelines. Each pipeline exposes a Grafana endpoint for querying and correlating traces with logs and metrics. If you are new to the Tracing API, see [What Can You Do with the Tracing API?](#what-can-you-do-with-the-tracing-api). If you manage observability infrastructure, see [Tracing API Workflows](https://docs.ionos.com/cloud/api-reference/observability/tracing-service/tracing-api-workflows.md).

### What Can You Do with the Tracing API?

Using the Tracing API, you can:

* **Create and manage pipelines:** Provision tenant-isolated pipelines that define the OTLP ingestion protocol and endpoint for your trace data.
* **Select the OTLP protocol:** Choose between OTLP HTTP and OTLP gRPC (Google Remote Procedure Call) per pipeline to match your exporter configuration.
* **Access the Grafana endpoint:** Retrieve the Grafana instance URL for each pipeline to query and visualize collected traces.
* **Rotate pipeline keys:** Generate a new authentication key for a pipeline to invalidate the previous one.

### Endpoints

The Tracing API is available at the following endpoints.

| **Location**       | **Region** | **Endpoint**                       |
| ------------------ | ---------- | ---------------------------------- |
| Frankfurt, Germany | `de-fra`   | `https://tracing.de-fra.ionos.com` |
| Berlin, Germany    | `de-txl`   | `https://tracing.de-txl.ionos.com` |
| Logroño, Spain     | `es-vit`   | `https://tracing.es-vit.ionos.com` |
| Worcester, UK      | `gb-bhx`   | `https://tracing.gb-bhx.ionos.com` |
| London, UK         | `gb-lhr`   | `https://tracing.gb-lhr.ionos.com` |
| Paris, France      | `fr-par`   | `https://tracing.fr-par.ionos.com` |
| Lenexa, US         | `us-mci`   | `https://tracing.us-mci.ionos.com` |
| Newark, US         | `us-ewr`   | `https://tracing.us-ewr.ionos.com` |
| Las Vegas, US      | `us-las`   | `https://tracing.us-las.ionos.com` |

To authenticate with the API, see [Authentication](https://docs.ionos.com/cloud/api-reference/observability/tracing-service/authentication.md). To make your first API call, see [Quick Start](https://docs.ionos.com/cloud/api-reference/observability/tracing-service/quick-start.md).

### Features

* **Protocol support:** The IONOS CLOUD Tracing API supports OTLP HTTP and OTLP gRPC protocols. You select one `protocol` per pipeline. Changing it later with [Ensure Pipeline](https://docs.ionos.com/cloud/api-reference/observability/tracing-service/pipelines/ensure-pipeline) reprovisions the ingestion route behind the same DNS name and may temporarily interrupt ingestion while you reconfigure your exporter.
* **Async provisioning:** Create and delete operations are asynchronous. Poll [Retrieve Pipeline](https://docs.ionos.com/cloud/api-reference/observability/tracing-service/pipelines/retrieve-pipeline) until `metadata.state` reaches `AVAILABLE` before connecting exporters.
* **Ensure semantics:** `PUT` operations use full-replacement semantics. Both `properties.name` and `properties.protocol` are required in every `PUT` request. The API returns `400` if either is missing.
* **One-time key retrieval:** The API returns the authentication key (`metadata.key`) only in the `201` create response and in [Rotate Key](https://docs.ionos.com/cloud/api-reference/observability/tracing-service/key/rotate-key) responses. Subsequent `GET` responses omit the key.
* **Pagination:** List operations use offset and limit parameters. The default page size is `100`. The maximum is `1000`. To retrieve the next page, increment `offset` by the `limit` value, or follow `_links.next` when it is present in the response.

### Benefits

* **Multi-source trace visibility:** The Tracing API accepts OTLP traces from IONOS CLOUD workloads, on-premises environments, and other clouds. You receive one Grafana endpoint per pipeline to query and correlate all collected traces with logs and metrics.
* **Regional data colocation:** Each pipeline is provisioned in one of nine metro locations. You reduce latency and meet local data-storage requirements by placing pipelines in the region closest to your workloads.
* **Secure-by-default ingestion:** Each pipeline carries a unique authentication key. The API returns this key only on creation and rotation. You can rotate the key at any time without reprovisioning the pipeline, limiting the blast radius of a compromised credential.
* **Protocol flexibility:** Each pipeline exposes either OTLP HTTP or OTLP gRPC, and the ingestion DNS name remains stable when you switch. You reconfigure only your exporter, not the pipeline endpoint.


---

# 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/api-reference/observability/tracing-service/overview.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.
