baseline-alerting

Name: baseline-alerting
Availability: InStock
Author: Razorpay

Generate standardized Prometheus baseline alerts for Razorpay microservices via PRs.

31|4|Updated Aug 24, 2021

Search Tags:#automation #rendering #deduplication #pr #prometheus #alert-rules #baseline-alerting

Ready to run

npx skills add https://github.com/razorpay/trino-gateway --skill baseline-alerting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: baseline-alerting
Source: https://github.com/razorpay/trino-gateway/tree/main/.agents/skills/baseline-alerting
Command: npx skills add https://github.com/razorpay/trino-gateway --skill baseline-alerting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jinja2, pyyaml, and includes scripts (resource) components.

What problem does it solve?

Baseline alerting standardizes and automates Prometheus alert rules for Razorpay microservices, ensuring consistent monitoring coverage and reproducible deployments via PRs to the alert-rules repository.

Core Features & Use Cases

End-to-end baseline alerting workflow spanning Reconnaissance, Service Analysis, Input Generation, Render + Dedup, Place + Validate, and PR Creation to ship baseline alerts.
Deduplication and migration: detects existing semantically equivalent alerts and prevents duplicates, with a migration path when needed.
PR-based delivery: renders alerts from templates, validates them, and creates a PR to update the alert-rules repository.
Use Case: Onboard a new microservice or refresh monitoring for an existing service by generating a complete baseline alert set.

Quick Start

Provide an inputs YAML and run the render pipeline to generate baseline-alerting rules, then validate and submit a PR.

Frequently Asked Questions about baseline-alerting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate generating Prometheus alert rules for microservices?▼

You can automate generating Prometheus alert rules by providing an inputs YAML and running a render pipeline that creates standardized baseline alerts. It then validates them with promtool and submits a PR to the alert-rules repository.

How does baseline alerting handle duplicate Prometheus alerts?▼

Baseline alerting handles duplicate Prometheus alerts by detecting existing semantically equivalent rules during the render and deduplication phase. It prevents duplicates and provides a migration path when existing rules need updating.

Do I need promtool and gh CLI to create baseline alert PRs?▼

Yes, you need promtool and gh CLI to create baseline alert PRs, along with Python 3.8+, git, and access to the alert-rules repository. These tools validate rendered rules and manage the PR submission.

What is the best way to standardize monitoring alerts across microservices?▼

The best way to standardize monitoring alerts is to use an automated rendering pipeline that generates baseline Prometheus alerts from templates. This ensures consistent monitoring coverage and reproducible deployments via PRs.

Can I update existing Prometheus alerts using an automated workflow?▼

Yes, you can update existing Prometheus alerts by running the render pipeline with updated inputs YAML. It handles migrations for existing semantically equivalent alerts and submits changes as a PR to the alert-rules repository.