This repository was archived by the owner on Sep 29, 2025. It is now read-only.
(EAI-1247) Prometheus alerts for 429 rate limit errors#864
Open
(EAI-1247) Prometheus alerts for 429 rate limit errors#864
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR adds Prometheus alerting rules to monitor and alert on HTTP 429 rate limit errors for the chatbot service in both staging and production environments.
- Adds two new alert rules:
HighRateLimitErrors(warning) andCriticalRateLimitErrors(critical) - Configures different thresholds and time windows for warning vs critical alerts
- Includes descriptive annotations with potential causes and troubleshooting guidance
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| packages/chatbot-server-mongodb-public/environments/staging.yml | Adds two Prometheus alert rules for monitoring 429 rate limit errors |
| packages/chatbot-server-mongodb-public/environments/production.yml | Adds identical Prometheus alert rules for monitoring 429 rate limit errors |
packages/chatbot-server-mongodb-public/environments/staging.yml
Outdated
Show resolved
Hide resolved
packages/chatbot-server-mongodb-public/environments/production.yml
Outdated
Show resolved
Hide resolved
mongodben
approved these changes
Aug 6, 2025
Collaborator
mongodben
left a comment
mongodben
left a comment
There was a problem hiding this comment.
assuming that this is copied from somewhere. for my eduction: how do we kno if the server logs with code="429" in such a way to support this?
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Jira: (EAI-1247) Prometheus alerts for 429 rate limit errors
Changes
stagingandproductionfor high numbers of rate limit errors