Automation Suite on Linux installation guide

Last updated Nov 13, 2025

Monitoring configuration

To provision enough resources for monitoring (see Using the monitoring stack), you should consider the number of vCPUs in the cluster and the amount of desired metric retention. Details on how to set the following monitoring resource configurations are provided next.

The following table describes the monitoring field details:

Parameter	Description
`prometheus_retention`	In days. This is the amount of days that metrics will be retained for the purpose of visualization in Grafana and manual querying via the Prometheus console. Default value is `7`.
`prometheus_storage_size`	In GB. Amount of storage space to reserve per Prometheus replica. A good rule of thumb is to set this value to: `0.65 * vCPU cores * (prometheus_retention / 7)` Example: If you set `prometheus_retention` to 14 days, and your cluster has 80 cores spread across 5 machines, this becomes: `0.65 * 80 * (14 / 7)` `52 * (2)` `104` Default value is `45` and should not be set lower. If Prometheus starts to run out of storage space, an alert will be triggered with specific remediation instructions. See here.
`prometheus_memory_limit`	In MB. Amount of memory to limit each Prometheus replica to. A good rule of thumb is to set this value to: `100 * vCPU cores * (prometheus_retention / 7)` Example: If you've set `prometheus_retention` to 14 days, and your cluster has 80 cores spread across 5 machines, this becomes: `100 * 80 * (14 / 7)` `8000 * (2)` `16000` Default value is `3200` for the single-node evaluation mode, and `6000` for the multi-node HA-ready production mode, and should not be set lower. If Prometheus starts to run out of memory, an alert will be triggered with specific remediation instructions. See here.

Example

"monitoring": {
  "prometheus_retention": 14,
  "prometheus_memory_limit": 16000,
  "prometheus_storage_size": 104
}"monitoring": {
  "prometheus_retention": 14,
  "prometheus_memory_limit": 16000,
  "prometheus_storage_size": 104
}

Optional: Configuring the monitoring solution

You can configure a cluster installation to exclude built-in monitoring components This option lets you use your own monitoring stack and provides flexibility for organizations with custom observability solutions.

You can exclude the following components: Prometheus/Grafana, Goldpinger, and Alerts.

The exclusion of these components is controlled through the exclude_components field in the cluster config.json file, as shown in the following example:

{
  "exclude_components": [
    "monitoring",
    "goldpinger",
    "alerts"
  ]
}{
  "exclude_components": [
    "monitoring",
    "goldpinger",
    "alerts"
  ]
}

You can enable or disable the monitoring stack after installation by updating the exclude_components list.

Note: During a cluster upgrade or migration, data related to external monitoring solutions is not migrated or retained. You are responsible for installing, upgrading, or migrating your monitoring stack and data, and for handling any compatibility issues that may occur due of Kubernetes version upgrades.

On this page

Optional: Configuring the monitoring solution

Was this page helpful?

PREVIOUSAI Center-specific configuration

NEXTOptional: Configuring the proxy server

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy