Skip to content

(EAI-1247) Prometheus alerts for 429 rate limit errors #864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

nlarew
Copy link
Collaborator

@nlarew nlarew commented Aug 6, 2025

Jira: (EAI-1247) Prometheus alerts for 429 rate limit errors

Changes

  • Add alerts to staging and production for high numbers of rate limit errors

@nlarew nlarew requested a review from Copilot August 6, 2025 19:12
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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) and CriticalRateLimitErrors (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

Copy link
Collaborator

@mongodben mongodben left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants