Skip to content

Commit 5fd7ab5

Browse files
mhyonMashaMSFT
andauthored
Updated for serverless (#33867)
--------- Co-authored-by: Masha Thomas (MSFT) <[email protected]>
1 parent ddfdb78 commit 5fd7ab5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

azure-sql/database/monitoring-metrics-alerts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,6 +83,7 @@ Here's the logic used for calculating Availability for every one-minute interval
8383
- If all connections fail due to user errors, availability is 100%.
8484
- If there are no connection attempts, availability is 100%.
8585
- If all connections fail due to system errors, availability is 0%.
86+
- Currently, the availability metric data isn't supported for the serverless compute tier, and displays 100%.
8687

8788
Availability metric is therefore a composite metric derived from following existing metrics:
8889

@@ -101,7 +102,6 @@ User errors include all connections that fail due to user configuration, workloa
101102

102103
- Examples of errors caused by user workload:
103104
- [Connection failure due to resource governance](troubleshoot-common-errors-issues.md?view=azuresql-db&preserve-view=true#resource-governance-errors)
104-
- Connection attempts to a serverless database that is in a paused state
105105

106106
- Examples of errors caused by user management:
107107
- Scaling up or down the database or elastic pool

0 commit comments

Comments
 (0)