> 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/observability/tracing-service/quick-start/access-traces-from-platform.md).

# Access Traces from the Platform

{% hint style="info" %}
**Prerequisite:** You must [<mark style="color:blue;">create a tracing pipeline</mark>](/cloud/observability/tracing-service/quick-start/send-traces-to-platform.md#create-a-pipeline) first to access Grafana.
{% endhint %}

## Obtain your Grafana URL via the API

You can obtain your Grafana instance address by sending a `GET` request to the server, for example `GET https://tracing.de-txl.ionos.com/pipelines`. The response contains the `grafanaEndpoint`. This information remains the same for all your tracing pipelines.

Using the URL in the `grafanaAddress`, you can access Grafana.

### How to Restrict Grafana access

Access to Grafana via SSO depends on IAM and the pipeline lifecycle. To effectively restrict Grafana access:

1. Remove or restrict the user in IAM for the relevant contract (so they cannot SSO).
2. Remove the user from the Grafana organization to clean up roles and memberships.

{% hint style="warning" %}
**Warning:**

* Changing privileges in the <code class="expression">space.vars.ionos\_cloud</code> API or the DCD without restricting the user’s IAM access may not immediately prevent Grafana SSO, even when pipelines are active or during the 30-day grace period.
* Removing a user only from the Grafana organization does not control SSO eligibility; ensure the user’s IAM access is revoked if complete removal is required.
  {% endhint %}

## Explore traces in Grafana

Traces are queryable through the Tempo data source, which is provisioned automatically in your Grafana instance. If you are new to Tempo, use the **Explore** view and the **Data sources** section in Grafana to search and view traces. The **Drill down** view expects an existing trace context and can show an error if you start there.

For more details on searching traces and correlating them with metrics and logs, see the official Grafana documentation:

* [<mark style="color:blue;">Tempo data source</mark>](https://grafana.com/docs/grafana/latest/datasources/tempo/)
* [<mark style="color:blue;">Configure trace to logs</mark>](https://grafana.com/docs/grafana/latest/datasources/tempo/configure-tempo-data-source/configure-trace-to-logs/)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/cloud/observability/tracing-service/quick-start/access-traces-from-platform.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.