> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/v19-en-us/parallels-ras-19-administrators-guide/session-management/monitoring-settings.md).

# Monitoring settings

The **Monitoring Settings** functionality allows you to add colors to thresholds to identify Warning and Critical levels for better aid to Administrators or helpdesk.

To configure monitoring settings, in the **Sessions** category or **Sessions** tabs, click **Tasks** > **Monitoring settings**. The dialog opens where you can configure settings for various session metrics:

1. Select a metric for which you want to enable color coding.
2. Specify a threshold in the **Warning** and **Critical** columns. The Warning threshold is denoted by the orange color. The Critical threshold is denoted by the red color.
3. If you want to see just the Critical color (red), then set both thresholds to the same value, in which case only the red color will be used when the threshold is reached.

When a metric with color coding enabled is below any of the specified thresholds, it is highlighted with the green color in the session list. When a threshold is reached, the value of a metric is highlighted using the corresponding threshold color (orange or red). Note that critical threshold value can be greater or equal to warning threshold value. In case both warning and critical values are equal then the critical color coding is used which is red.

Monitoring Settings are set globally, which means that other RAS admins will be able to see and change them.


---

# 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.parallels.com/landing/ras-admin-guide/v19-en-us/parallels-ras-19-administrators-guide/session-management/monitoring-settings.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.