What problem does it solve?
Configuring alert rules in Nightingale by hand is error-prone: you must pick the right business group and data source, write correct PromQL or SQL, and match each data source type's rule_config schema. This Skill automates the entire process, either by importing pre-validated rule packs from the integrations catalog or by hand-writing custom rules with verified schemas.
Core Features & Use Cases
- Import validated rule packs: Browse and import ready-made alert rules for standard components (Linux, MySQL, Redis, Kafka, PostgreSQL, Elasticsearch, etc.) from the integrations directory, importing a whole pack, a batch, or a single named rule.
- Hand-write custom rules: Create rules for Prometheus, Loki, Elasticsearch, OpenSearch, MySQL, PostgreSQL, ClickHouse, Doris, TDengine, VictoriaLogs, and Host heartbeat monitoring, with per-datasource reference docs for the exact rule_config structure.
- Schema probing for SQL sources: Verify real databases, tables, and columns via list_databases/list_tables/describe_table before generating SQL, avoiding runtime errors from guessed names.
- Use Case: A user asks to "add a set of alert rules for MySQL". The Skill checks available integration packs, prefers the categraf variant after probing metric data, imports the pack bound to the correct data source, and reports created/skipped/failed counts.
Quick Start
Ask the assistant to configure a set of common alert rules for your MySQL data source in the default business group.