> 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/update-monitoring-pipeline.md).

# Update a Monitoring Pipeline

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

To update the monitoring pipeline details, follow these steps:

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

2\. In the **Monitoring Service** overview page, select the monitoring pipeline to update.

3\. In **View & Edit**, update the monitoring pipeline details needed:

* **Properties:** Refers to the generic properties of the monitoring pipeline. To update these details, see [<mark style="color:blue;">Create a Monitoring Pipeline</mark>](/cloud/observability/monitoring-service/dcd-how-tos/create-monitoring-pipeline.md).
* **Renew Key:** This option allows you to renew the API key for the monitoring pipeline. The key is used to configure your metrics agent to authenticate against the pipeline's remote-write endpoint.

4\. Click **Save** to update the monitoring pipeline details with the changes made.

{% hint style="success" %}
**Result:** The monitoring pipeline is successfully updated.
{% endhint %}


---

# 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/update-monitoring-pipeline.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.