Usage Monitoring and SCU (Security Compute Unit) Management

Atlanta, USA

Cloud2BR OSS - Learning Hub

Last updated: 2026-08-04

---

References

• Manage SCU (Security Compute Unit) usage
• SCU (Security Compute Unit) capacity model

Objective

Maintain predictable cost and uninterrupted analyst workflows by actively monitoring and tuning SCU (Security Compute Unit) usage.

Monitoring dimensions

Dimension	Example value
Session source	Standalone, embedded, or automation trigger
Category	Prompt, promptbook, or agent execution
Plugin usage	Which integration sources drive consumption
Initiator	Which teams or users consume most capacity

Capacity management cycle

1. Review dashboard trends by day and by workflow type.
2. Apply filters to isolate high-consumption patterns.
3. Tune provisioned and overage settings based on observed demand.
4. Export and share usage evidence with stakeholders.

Guardrails

• Capacity nearing limit alert review process.
• Capacity exceeded incident response workflow.
• Change approvals for significant SCU (Security Compute Unit) increases.
• Monthly cost and value review cadence.