Skip to main content

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.

Checks that Azure SQL database CPU utilization is being monitored.

​
Why This Matters

Unmonitored infrastructure can degrade silently until services fail. CPU spikes, memory exhaustion, storage depletion, and latency increases are early warning signs of performance issues, resource exhaustion attacks, or misconfiguration. Proactive monitoring is required by SOC 2 (CC7.1) and ISO 27001 (A.12.1.3).

​
What DSALTA Checks

DSALTA connects to your Microsoft Azure environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → Microsoft Azure.

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Sign in to the Azure Portal and navigate to the affected Azure SQL resource.
  2. In the resource menu, go to Monitoring → Alerts → Create alert rule.
  3. Under Condition, select the cpu_percent metric.
  4. Configure the alert logic to trigger when cpu_percent cpu_percent exceeds 80% sustained.
  5. Set the evaluation period (e.g., every 5 minutes, over 15 minutes).
  6. Under Actions, select or create an action group to deliver alerts to your team.
  7. Name the alert rule and click Create.
  8. Consider scaling up the DTU/vCore tier, optimizing expensive queries, or adding read replicas.
  9. Once the alert rule is active, DSALTA will detect the configuration on the next sync and update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the Microsoft Azure integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in Microsoft Azure.