> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics.md).

# Metrics

Reference page to Servoy Cloud Environment metrics

## Overview

Each Servoy Cloud environment shows a higher level overview displayed as tiles of the following metrics:

1. [Users](/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/users.md)
2. [System Health](/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/system-health.md)
3. [Databases](/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/databases.md) (Not supported for [Remote Environments](https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/pages/eg11jvoePw6GRviVLUBP#id-5.-remote-on-premise))
4. [Log Activity](/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/log-activity.md)
5. [Application Performance](/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/app-performance.md)
6. [Query Performance](/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/query-performance.md)

{% hint style="info" %}
Clicking on the tile will navigate to a detailed view.
{% endhint %}

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2Fgit-blob-da0ce28fd5e725a4e96ed19a81021705fa1de536%2Fccc_environment_metrics.png?alt=media" alt=""><figcaption></figcaption></figure>

## Performance alerts

Performance alerts are displayed in tiles on the Environment Details page. These alerts indicate the system's performance status over the last hour based on the following criteria:

### Needs Attention

* **System Health**: Indicates "Needs Attention" if the CPU has any "Needs Attention" performance alerts.
* **Log Activity**: Indicates "Needs Attention" if there are 10 or more non-fatal errors.
* **Application Performance**: Indicates "Needs Attention" if there are any "Needs Attention" performance alerts, but none are "Critical".
* **Query Performance**: Indicates "Needs Attention" if there are any performance alerts, but none are "Critical".

### Critical

* **System Health**: Indicates "Critical" if any of the System Health metrics have "Critical" performance alerts, or if there are any system interruptions.
* **Log Activity**: Indicates "Critical" if there are any fatal errors.
* **Application Performance**: Indicates "Critical" if there are any "Critical" performance alerts.
* **Query Performance**: Indicates "Critical" if there are any "Critical" performance alerts.

## How to access

You can access the Environment Details from various locations within the Cloud Control Center:

* The "Environments at-a-glance" section, accessible through the Home menu item.
* The Environment view within Application Details.


---

# 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.servoy.com/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics.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.