> 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/monitoring-service/dcd-how-tos/view-monitoring-pipelines.md).

# View Monitoring Pipelines

Once a monitoring pipeline is successfully created, the instance is listed on the **Monitoring Service** overview page.

To view the monitoring pipeline details, follow these steps:

1\. In the **DCD**, go to **Menu** > **Observability** > **Monitoring Service**.

{% hint style="success" %}
**Result:** A list of monitoring pipelines created is displayed. For every instance listed, you can view the following details:

* **NAME:** Displays the name of the monitoring pipeline. Select the name to view the respective pipeline details.
* **STATE:** Displays the state of the monitoring pipeline. Possible values are as follows:
  * **Available:** The monitoring pipeline is available and in good condition.
  * **Provisioning:** When the monitoring pipeline is either being updated or created.
  * **Destroying:** When the monitoring pipeline is being deleted.
  * **Failed:** When the monitoring pipeline creation or update has failed.
* **LOCATION:** Displays the location where the monitoring pipeline is created.
* **CREATION DATE:** Displays the date of creation of the monitoring pipeline.
* **OPTIONS:** Select ![Options menu](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-0820a9f96e75bb8fa664037bb8f38d7d825394d7%2Fthree-dots.png?alt=media) to perform the following:
  * **View & Edit:** You can view and edit the selected monitoring pipeline details.
  * **Copy remote-write endpoint:** Copy the remote-write endpoint of the monitoring pipeline to use in your metrics agent configuration.
  * **Copy Pipeline UUID:** Copy the UUID of the monitoring pipeline to use this identifier in the API calls.
  * **Delete Pipeline:** Deletes the selected monitoring pipeline. In the dialog box that appears, select **Delete** to confirm deletion. For more information, see [<mark style="color:blue;">Delete a Monitoring Pipeline</mark>](/cloud/observability/monitoring-service/dcd-how-tos/delete-monitoring-pipeline.md).
    {% endhint %}

![List of Monitoring pipelines](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-3c7bbab3c004415b54d7bd4a8979add2d9d100ea%2Foverview-monitoring-pipelines.png?alt=media)

## View details of a selected Monitoring Pipeline

For the selected monitoring pipeline, you can view the following details:

* **Properties:** The following system information related to the monitoring pipeline is displayed:
  * **Name:** Displays the name of the monitoring pipeline.
  * **Location:** Displays the location of the monitoring pipeline.
  * **Status:** Displays the state of the monitoring pipeline.
  * **UUID:** The unique ID of the monitoring pipeline.
  * **Creation date:** Specifies the date and time of monitoring pipeline creation.
  * **Remote-write endpoint:** The endpoint URL used to push metrics to the monitoring pipeline.

![View monitoring pipeline properties](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-dad9eefc21aabc17a8723f72786d66642b5f5c16%2Fview-monitoring-pipeline-properties.png?alt=media)


---

# 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/observability/monitoring-service/dcd-how-tos/view-monitoring-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.
