• Lead Time Required28 day(s)

• Control Plane Latency KPI (ARM Fundamentals) 

Scope: Products with ARM RPs creating new Resource Types or changing existing ones.

• • ARM Fundamentals KPI Definitions (https://armwiki.azurewebsites.net/fundamentals/overview.html)

• • Getting ARM RP Consistency and CLI Sign-off (https://armwiki.azurewebsites.net/fundamentals/armrp_apex_signoff/getting-apex-launch-readiness-signoff.html)

• • Control Plane Latency reports to assess overall performance:

• • • RP: Control Plane Latency Report

• • • RPaaS RP: UserRP Latency Report

__________________________

Control Plane Latency KPI (ARM Fundamentals) 

OWNER: ARM Control Plane KPIs Team

(APEX) Required by: Public Preview

(What) KPI Description:

The Control Plane Latency KPI tracks each Resource Provider's (RPs) operations’ running times. The goal is for all RP operations to return a response in under 1 second at the P99 level.

(Why) Business Impact:

The latency of Azure control plane operations directly affects customers' experiences creating, updating, and deleting resources. Each of these scenarios is critical to providing high quality Azure customer experiences. Improvements in control plane latency are indicative of a better and more dependable cloud provider.

(Logic) KPI Calculation Logic:

All operations should return in less than or equal to 1s at the 99th percentile (P99). For long running async operations, this KPI measures the time to the first synchronous 200/201/202 response and IS NOT tracking the latency of the long running response.

(How) GETTING TO GREEN (IN SLA):

Look at spikes in latency across different timespans to understand your RP's operations performance, pick out correlationIds where durationInMilliseconds > 1000, filter by these correlationIds within your RPs logs to understand slow request paths. Learn more / investigate here: https://aka.ms/cplatencywiki