Introduction

This document covers how to configure alert thresholds for public cloud metrics within the Integrations module. It explains the steps required to set up and customize threshold levels for various metrics from your cloud infrastructure, helping you to monitor and manage cloud resources by receiving alerts when performance or utilization exceeds defined limits.

By setting appropriate thresholds, users can enhance resource management and prevent potential performance issues across public cloud environments.

Set Alert Thresholds

In our current design, alerts are triggered based on the thresholds configured by the user.

Scenario 1

Where a customer wants to receive an alert when the instance value drops below a certain threshold, the critical threshold should be set lower than the warning threshold. In this case, the criticality increases as the value decreases (for example, memory utilization).

Example

If the customer wants an alert when the instance value falls below 100 units, they should set the critical threshold at 100 units and the warning threshold above 100 units (for example, 110). A critical alert will be triggered when the value falls to 100 units or lower, and a warning alert will be triggered when the value falls to 110 units or lower.

Scenario 2

Where a customer wants to receive an alert when the instance value exceeds a certain threshold, the critical threshold should be set higher than the warning threshold. Here, the criticality increases as the value rises (for example, CPU utilization).

Example

If the customer wants an alert when the instance value exceeds 90 units, they should set the critical threshold at 90 units and the warning threshold below 90 units (for example, 80). A critical alert will be triggered when the value rises to 90 units or higher, and a warning alert will be triggered when the value rises to 80 units or higher.