Add ARM throttling dashboards for FXCI subscriptions#290
Closed
jwmossmoz wants to merge 5 commits into
Closed
Conversation
No schema changes between 2020-09-01-preview and 2025-04-01-preview per Microsoft change log.
The older MetricsChartPart format lacked the namespace field, causing "isMdmMetricEnabled" errors for subscription-level ARM metrics. Use MonitorChartPart with resourceMetadata and microsoft.resources/subscriptions namespace.
Traffic metric supports Count (7), not Sum (1). Use proper ARM resource provider casing for namespace.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why dashboard-first
The subscription is showing ARM
429throttling, but the right alert threshold still needs tuning. This PR adds a stable dashboard reference point first for the subscription-levelTrafficandLatencymetrics, plus drill-down guidance for proving subscription-bucket exhaustion from client headers.Validation
terraform fmtran on the two changed dashboard filesterraform/azure_fxciandterraform/azure_trusted_fxciis still blocked in this environment by the repo's AWS provider configuration failing STS credential validation (InvalidClientTokenId) duringterraform init -backend=false