azure: emit Azure API rate-limit metrics#666
Draft
HadrienPatte wants to merge 1 commit into
Draft
Conversation
Azure API responses include X-Ms-Ratelimit-Remaining-* headers that
report how much of the request budget is left for the subscription or
tenant scope. Surfacing these as Prometheus metrics lets operators see
how close they are to throttling before requests start failing.
Add a per-retry pipeline policy (rateLimitMetricsExtractor) that runs
inside the azcore client pipeline. On each response it parses the
remaining-budget headers and records two new gauges on the existing
Azure IPAM allocator Metrics struct:
* `cilium_operator_azure_ratelimit_remaining{description, subscription_id}`
* `cilium_operator_azure_ratelimit_remaining_resource{policy, subscription_id}`
subscription_id is left empty for tenant-scoped descriptions
(tenant-reads, tenant-writes, ...) since the budget is shared across
the tenant and labeling it with one subscription would be misleading.
Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
HadrienPatte
force-pushed
the
hadrien/1.19/azure-metrics
branch
from
78405f9 to
549f695
Compare
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.
Azure API responses include X-Ms-Ratelimit-Remaining-* headers that report how much of the request budget is left for the subscription or tenant scope. Surfacing these as Prometheus metrics lets operators see how close they are to throttling before requests start failing.
Add a per-retry pipeline policy (rateLimitMetricsExtractor) that runs inside the azcore client pipeline. On each response it parses the remaining-budget headers and records two new gauges on the existing Azure IPAM allocator Metrics struct:
cilium_operator_azure_ratelimit_remaining{description, subscription_id}cilium_operator_azure_ratelimit_remaining_resource{policy, subscription_id}subscription_id is left empty for tenant-scoped descriptions (tenant-reads, tenant-writes, ...) since the budget is shared across the tenant and labeling it with one subscription would be misleading.