Menú
Convert Prometheus alerting rules into Guance monitor JSON and validate all generated DQL.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Generate, repair, or review Guance Dashboard JSON from real metrics CSV files, tag metadata, and resource-catalog or custom-object CSV/JSON data.
Generate Guance monitor JSON from CSV metric files for any component.
Convert Grafana dashboard JSON into Guance dashboard JSON with a fully self-contained skill package. Use when the user wants to analyze Grafana dashboards before conversion, run conversion, audit conversion gaps, improve units or PromQL compatibility with LLM-assisted review, repair panel or variable mappings, preserve settings, groups, and vars as much as possible, validate generated Guance dashboard JSON against the bundled schemas, or debug why a Grafana dashboard does not convert cleanly.
Use the owl CLI for Guance queries, diagnostics, root-cause analysis, and structured Markdown reports.
Generate, fix, explain, and review DQL; final executable DQL must pass dqlcheck item by item.
Convert, validate, and explain Alibaba Cloud SLS queries as GuanceDB DQL.
| name | alert_manager |
| author | liurui |
| description | Convert Prometheus alerting rules into Guance monitor JSON and validate all generated DQL. |
Use this skill when the user wants to convert Prometheus alerting rules into Guance monitor configuration.
The input must be an alerting rule definition with fields such as alert, expr, for, labels, and annotations. Do not treat Alertmanager routing configuration such as route, receivers, inhibit_rules, or mute_time_intervals as convertible monitor rules.
Before writing DQL, confirm the metric mapping:
| Required field | Purpose |
|---|---|
component | Output directory and stable monitor identity |
source_metric | Metric name in the source rule |
dataSource | Guance data source or measurement |
field | Guance field name |
groupBy | Monitor grouping tag |
fieldType | Field data type |
fieldFunc | Recommended aggregation function |
If any key mapping is missing, stop and ask for the missing mapping instead of inventing DQL.
monitor skill.checkers[].jsonScript.targets[].dql and checkers[].extend.querylist[].query.q for each rule.checkerOpt.rules and extend.rules synchronized.dqlcheck before final output.Map labels.severity to Guance statuses when possible: critical, warning, error, or info. If severity is missing, default to critical and state that the value was defaulted.
Stop instead of guessing when the expression uses multi-metric binary operations, complex and or or expressions, label_replace, histogram_quantile, complex subqueries, unknown recording rules, or rate semantics that cannot be safely mapped.