> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Cache for Redis CPU utilization should be monitored

> Checks that Azure Cache for Redis CPU utilization is being monitored.

Checks that Azure Cache for Redis CPU utilization is being monitored.

## About

When you connect Microsoft Azure to DSALTA, the platform retrieves the list of resources in your environment using read-only API access. DSALTA then checks whether this configuration is in place. If it is not, DSALTA activates this check so you can remediate it.

## Why This Matters

Infrastructure that is not monitored fails silently until it impacts users. Tracking key metrics — and alerting when they cross a threshold — lets you act before a small issue becomes an outage. Proactive monitoring is required by SOC 2 and ISO 27001.

## How to Fix

**Before you begin**

* Ensure you have **Contributor** or **Monitoring Contributor** access to the Azure subscription.
* Confirm that you have Azure Cache for Redis resources for which you want to create the alert.

**Create the Azure Monitor alert**

1. Sign in to the [Azure Portal](https://portal.azure.com/) and navigate to your **Azure Cache for Redis** resource.
2. In the left menu, under **Monitoring**, select **Alerts → Create → Alert rule**.
3. Under **Condition**, select the **Server Load (percentProcessorTime)** signal.
4. Configure the alert logic to alert when CPU exceeds 80%, and set the evaluation frequency (for example, every 5 minutes).
5. Under **Actions**, select or create an **action group** to deliver notifications to your team (email, SMS, or webhook).
6. Enter an alert rule name and description, then click **Create**.

Once the alert rule is active for **Server Load (percentProcessorTime)**, DSALTA retrieves the change on the next sync and sets the check status to **Passing**.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    This check runs automatically every 24 hours while the Microsoft Azure integration is connected. You can also trigger a manual sync from **Integrations** in the sidebar.
  </Accordion>

  <Accordion title="What happens if it keeps failing?">
    A failing check appears in your **Data Library → Tests** dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
  </Accordion>

  <Accordion title="Can I exclude this check?">
    Yes. If it does not apply to your environment, mark it as **Not Applicable** with a justification. The exclusion is documented for auditors.
  </Accordion>

  <Accordion title="Does DSALTA change my Microsoft Azure configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Microsoft Azure.
  </Accordion>
</AccordionGroup>