Add Postman API monthly request limit metric #4667
Merged
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
Adds a new Prometheus gauge metric
postman_api_monthly_requests_limitto capture the total monthly API request limit from Postman'sRateLimit-Limit-Monthresponse header.Background
Postman's monthly API rate limit is shared between TruffleHog scanner usage and the customer's own direct API usage. Our existing alert tracks scanner usage (
postman_api_requests) and remaining requests (postman_api_monthly_requests_remaining), but we couldn't distinguish between scanner and customer consumption when alerts fired.Changes
postman_api_monthly_requests_limitgauge metric to metrics.gohandleRateLimitsfrom theRateLimit-Limit-MonthheaderThis enables more actionable alerting--we can now identify whether high consumption is from our scanner (suggest increasing scan interval) or from the customer's own usage (advise them to reduce direct API calls).
Checklist:
make test-community)?make lintthis requires golangci-lint)?