> 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/overview/features-benefits.md).

# Features and Benefits

With a properly implemented Monitoring Service and various metrics, the following is a brief list of advantages of Monitoring Service for clients:

* **Centralized Metric Aggregation** Users can push metrics from various Prometheus-compatible agents to a central endpoint, where the service aggregates and stores them for comprehensive analysis.
* **Unified Querying Interface** Metrics and logs (from the logging service) are accessible through a single Grafana instance, allowing users to perform detailed queries and gain insights across all their data sources.
* **Predefined DBaaS Dashboards** Grafana includes predefined dashboards for DBaaS PostgreSQL, MariaDB, and In-Memory DB. For dashboard coverage and prerequisites, see [<mark style="color:blue;">Predefined DBaaS Grafana Dashboards</mark>](/cloud/databases/databases/dbaas-grafana-dashboards.md).
* **Scalable Architecture** The service is designed to handle extensive volumes of metrics, with the ability to scale up or down according to user needs, ensuring consistent performance regardless of workload.
* **High-Performance Data Processing** Optimized for speed and efficiency, the service delivers rapid data ingestion, aggregation, and querying, enabling efficient monitoring and analysis.

## Benefits

Besides all the topics listed in the features set, there are some more business-related benefits:

* **Metrics Unification:** Unify metrics across multiple data centers and applications, providing a holistic view of infrastructure and application performance.
* **Reduced Cost:** By centralizing and scaling the monitoring infrastructure, users can lower costs associated with maintaining and operating separate monitoring solutions.
* **Enhanced Data Consistency:** Aggregating all metrics in one place ensures consistent and accurate data, improving the reliability of insights and reporting.
* **In-Depth Analysis:** Leverages Grafana's powerful visualization and exploration capabilities to uncover insights from metric data.

{% hint style="info" %}
**Note:** All sub-user accounts in Grafana have at least a `Viewer` role, which allows them to see dashboards. The primary account owner can assign additional roles to sub-users as needed.
{% 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/overview/features-benefits.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.