> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/diagnostics-overview.md).

# Observability

Continuous monitoring of your cloud infrastructure in the DuploCloud Portal

DuploCloud ships with a standard suite of observability tools built into the platform. An extensible add-on suite of advanced diagnostic and monitoring tools, the DuploCloud Advanced Observability Suite based on OpenTelemetry, is also available for a monthly cost.

* The **Standard** Edition includes:
  * Logging using OpenSearch and Kibana
  * Metrics using Prometheus and cloud provider solutions like CloudWatch for AWS, Azure Monitoring for Azure, and Cloud Monitoring for GCP.
  * Alerting is limited to cloud services using CloudWatch. Users can wire third-party alerting solutions, such as Sentry, Pager Duty, etc., as described [here](/docs/automation-platform/overview-2/use-cases/faults-and-alerting.md).
  * No APM is included.<br>
* The **Advanced Edition** is a comprehensive add-on suite based on OpenTelemetry and includes:
  * Logging using [Loki](https://grafana.com/oss/loki/)
  * Metrics using [Mimir](https://grafana.com/products/cloud/metrics/)
  * Traces using [Tempo](https://grafana.com/products/cloud/traces/)
  * Profiles using [Pyroscope](https://grafana.com/products/cloud/profiles-for-continuous-profiling/)
  * Alerting using Grafana [Alert Manager](https://grafana.com/products/cloud/alerting/).
  * Visualization and Dashboards utilize Grafana.
  * Comprehensive APM capability is built by linking all the components together.

{% hint style="info" %}
Open Telemetry requires a Kubernetes cluster for deployment. It comprises approximately 20 Kubernetes components.
{% 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.duplocloud.com/docs/automation-platform/diagnostics-overview.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.