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

# Manage Central Monitoring

{% hint style="info" %}
**Central Monitoring** is a prerequisite for letting integrated <code class="expression">space.vars.ionos\_cloud</code> products forward metrics to Monitoring Service on your behalf. Activating it on your contract gives you region-level control over metric ingestion. Activate Central Monitoring from the [<mark style="color:blue;">DCD</mark>](#turn-on-central-monitoring-for-a-region) or the [<mark style="color:blue;">Monitoring API</mark>](/cloud/observability/monitoring-service/api-how-tos.md). To find out which products integrate with Central Monitoring, contact your account manager or [<mark style="color:blue;">IONOS CLOUD Support</mark>](https://docs.ionos.com/cloud/support/general-information/contact-information).
{% endhint %}

Activate Central Monitoring on your contract before any product can ingest metrics on your behalf. The DCD provides a per-region toggle that controls this contract-level flag.

{% hint style="info" %}
**Prerequisite:** Ensure you have the corresponding permissions to manage the Monitoring Service. Only contract administrators, owners, and users with **Access and manage Monitoring** privileges can activate or deactivate Central Monitoring. For more information, see [<mark style="color:blue;">Set User Privileges</mark>](/cloud/observability/monitoring-service/dcd-how-tos/set-privileges-monitoring-service.md).
{% endhint %}

## Turn on Central Monitoring for a region

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

2\. Select the **Central Monitoring** drop-down list.

![Turn on Central Monitoring toggle in the DCD](/files/s1CnA0O68NRNELo31rwn)

3\. Toggle the **STATE** to activate Central Monitoring for the selected region.

4\. In the confirmation dialog, select **Confirm**.

{% hint style="success" %}
**Result:** Central Monitoring is activated on your contract for the selected region. Supported products begin ingesting metrics in that region. You can view the remote-write endpoint, certificate, and API key under **Connection Details**.
{% endhint %}

## View connection details

When metrics are activated for an integrated product, its tag appears in the Central Monitoring view within the DCD. Connection details include the remote-write endpoint, certificate, and API key for the selected region.

![Connection details for Central Monitoring](/files/2rkESxhrV1UTiw5xkQWJ)

## Turn Off Central Monitoring for a region

1\. Select the **Central Monitoring** drop-down list.

2\. Toggle the **STATE** to deactivate Central Monitoring for the selected region.

3\. In the confirmation dialog, select **Confirm**.

{% hint style="success" %}
**Result:** Central Monitoring is not available on the contract for the selected region. Central Monitoring stops accepting metrics in that region regardless of whether products are still sending data, and the connection details are hidden.
{% 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 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/monitoring-service/dcd-how-tos/central-monitoring.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.