Merge pull request #368 from abkumbha36/patch-1

v-regandowner · web-flow · commit b5c106130562 · 2026-05-04T17:47:00.000-04:00
Enhance burstable compute description in concepts-compute.md
diff --git a/articles/postgresql/compute-storage/concepts-compute.md b/articles/postgresql/compute-storage/concepts-compute.md
@@ -40,7 +40,7 @@ After you create a server for the compute tier, you can change the number of vCo
 You can select compute resources based on the tier, vCores, and memory size. vCores represent the logical CPU of the underlying hardware.
 
 > [!IMPORTANT]  
-> Burstable compute is for workloads that stay idle or below baseline most of the time. If CPU runs near or above baseline for long periods, credits deplete and the server might become unreachable.  
+> Burstable compute is for workloads that stay idle or below baseline most of the time. If CPU runs near or above baseline for long periods, credits deplete and the server might become unreachable.  This tier is primarily designed for nonproduction scenarios such as development, staging, or testing, does not qualify for 24/7 support, and root cause analysis (RCA) may not be provided.
 >
 > For these workloads, it's recommended to:  
 > - Monitor **CPU Credits Remaining** in Azure Monitor and set alerts for low credits.  

Original file line number	Diff line number	Diff line change
`@@ -40,7 +40,7 @@ After you create a server for the compute tier, you can change the number of vCo`
`40`	`40`	`You can select compute resources based on the tier, vCores, and memory size. vCores represent the logical CPU of the underlying hardware.`
`41`	`41`
`42`	`42`	`> [!IMPORTANT]`
`43`		`-> Burstable compute is for workloads that stay idle or below baseline most of the time. If CPU runs near or above baseline for long periods, credits deplete and the server might become unreachable.`
	`43`	`+> Burstable compute is for workloads that stay idle or below baseline most of the time. If CPU runs near or above baseline for long periods, credits deplete and the server might become unreachable. This tier is primarily designed for nonproduction scenarios such as development, staging, or testing, does not qualify for 24/7 support, and root cause analysis (RCA) may not be provided.`
`44`	`44`	`>`
`45`	`45`	`> For these workloads, it's recommended to:`
`46`	`46`	`> - Monitor CPU Credits Remaining in Azure Monitor and set alerts for low credits.`