> 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/tracing-pipelines.md).

# Tracing Pipelines

A tracing pipeline is an instance of the Tracing Service that provides authenticated ingestion endpoints for your traces.

When you create a tracing pipeline, you select the pipeline name and ingestion protocol. The service then provisions protocol-specific ingestion details and returns metadata such as:

* A unique pipeline ID
* Pipeline state and timestamps
* A trace ingestion key
* A protocol-specific trace endpoint
* A `grafanaEndpoint` for trace exploration

## Regional API endpoint

To create and manage tracing pipeline instances, send requests to the regional Tracing Service API endpoint.

Example regional endpoint:

* Berlin: `https://tracing.de-txl.ionos.com/pipelines`
* Frankfurt: `https://tracing.de-fra.ionos.com/pipelines`
* London: `https://tracing.gb-lhr.ionos.com/pipelines`
* Worcester: `https://tracing.gb-bhx.ionos.com/pipelines`
* Paris: `https://tracing.fr-par.ionos.com/pipelines`
* Logroño: `https://tracing.es-vit.ionos.com/pipelines`
* Lenexa: `https://tracing.us-mci.ionos.com/pipelines`
* Las Vegas: `https://tracing.us-las.ionos.com/pipelines`
* Newark: `https://tracing.us-ewr.ionos.com/pipelines`

## Pipeline protocols

Each tracing pipeline is configured with one ingestion protocol:

* `otlp-http`
* `otlp-grpc`

The selected protocol determines the endpoint shape exporters use for ingestion.

## Access control

Non-admin users need the **Access and manage Tracing** privilege to create, update, rotate keys for, or delete tracing pipelines.

## Contract limitations

There is a maximum number of tracing pipelines you can create per contract. The default value is 10. If you need a higher limit, contact [<mark style="color:blue;">IONOS CLOUD Support</mark>](https://docs.ionos.com/cloud/support/general-information/contact-information) team to discuss your specific requirements and adjust the limits accordingly.


---

# 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/tracing-pipelines.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.