SkillsAdd

davidcastagnetoa/skills

alertmanager_standalone

Alertmanager independiente para routing de alertas del pipeline KYC con integraciones externas

First seen Mar 3, 2026

Installation

$ npx skills add davidcastagnetoa/skills --skill alertmanager_standalone
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

alertmanager-query Similar name
victoriametrics/skills

Query AlertManager via curl using the v2 API. Use when listing active/silenced alerts, creating…

214 installs

Also in this package

Other skills from davidcastagnetoa/skills · top by installs.

npx skills add davidcastagnetoa/skills
traefik 116 prisma-nestjs-patterns 58 easyocr 50 exif_metadata_analyzer 30 c4_model_structurizr 28 configurable_thresholds 25 alembic 23 insightface_arcface 19 asyncpg 19 github_actions_cicd 16

Browse all from davidcastagnetoa/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,407 B
  • docs SUMMARY.md 125 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 12 installs

SKILL.md

alertmanager_standalone

Prometheus Alertmanager desplegado como componente independiente para gestionar el ciclo de vida completo de las alertas del pipeline KYC. Maneja routing inteligente de alertas, silencing durante ventanas de mantenimiento, agrupacion de alertas relacionadas e integracion con canales de notificacion como PagerDuty y Slack.

When to use

Usa esta skill cuando necesites configurar o gestionar Alertmanager como servicio separado de Prometheus para el pipeline KYC. Pertenece al observability_agent y se aplica cuando hay que definir reglas de routing, configurar receptores de notificaciones, o gestionar silences y inhibiciones de alertas criticas del sistema de verificacion.

Instructions

  1. Desplegar Alertmanager como contenedor independiente en el cluster:

``yaml # docker-compose.alertmanager.yml services: alertmanager: image: prom/alertmanager:v0.27.0 ports: - "9093:9093" volumes: - ./alertmanager/alertmanager.yml:/etc/alertmanager/alertmanager.yml - alertmanager-data:/alertmanager command: - '--config.file=/etc/alertmanager/alertmanager.yml' - '--storage.path=/alertmanager' - '--cluster.listen-address=0.0.0.0:9094' restart: unless-stopped ``

  1. Configurar el routing de alertas con receptores diferenciados por severidad:

```yaml # alertmanager.yml global: resolve_timeout: 5m

route: receiver: 'slack-default' groupby: ['alertname', 'module'] groupwait: 30s groupinterval: 5m repeatinterval: 4h routes: - match: severity: critical receiver: 'pagerduty-kyc' group_wait: 10s - match: module: liveness receiver: 'slack-antifraude' - match: severity: warning receiver: 'slack-default' ```

  1. Configurar los receptores de PagerDuty para alertas criticas del pipeline:

``yaml receivers: - name: 'pagerduty-kyc' pagerdutyconfigs: - servicekeyfile: '/etc/alertmanager/secrets/pagerdutykey' severity: 'critical' description: '{{ .CommonAnnotations.summary }}' details: module: '{{ .CommonLabels.module }}' sessioncount: '{{ .CommonAnnotations.affectedsessions }}' ``

  1. Configurar el receptor de Slack para alertas de severidad warning:

``yaml - name: 'slack-default' slackconfigs: - apiurlfile: '/etc/alertmanager/secrets/slackwebhook' channel: '#kyc-alerts' title: '[{{ .Status | toUpper }}] {{ .CommonLabels.alertname }}' text: '{{ .CommonAnnotations.description }}' sendresolved: true - name: 'slack-antifraude' slackconfigs: - apiurlfile: '/etc/alertmanager/secrets/slack_webhook' channel: '#kyc-antifraude' title: 'Alerta Liveness: {{ .CommonLabels.alertname }}' text: '{{ .CommonAnnotations.description }}' ``

  1. Definir reglas de inhibicion para evitar cascadas de alertas:

``yaml inhibitrules: - sourcematch: severity: 'critical' targetmatch: severity: 'warning' equal: ['alertname', 'module'] - sourcematch: alertname: 'KYCServiceDown' target_match: alertname: 'KYCHighLatency' equal: ['module'] ``

  1. Definir las alerting rules en Prometheus apuntando al Alertmanager independiente:

```yaml # prometheus.yml alerting: alertmanagers: - static_configs: - targets: ['alertmanager:9093']

rulefiles: - '/etc/prometheus/rules/kycalerts.yml' ```

  1. Crear reglas de alerta especificas para el pipeline KYC:

``yaml # kycalerts.yml groups: - name: kyc-pipeline rules: - alert: KYCHighFraudRate expr: rate(kycfrauddetectedtotal[5m]) > 0.1 for: 2m labels: severity: critical module: antifraud annotations: summary: "Tasa de fraude anormalmente alta" description: "Se detectan mas de 0.1 fraudes/s en los ultimos 5 minutos" - alert: KYCVerificationLatencyHigh expr: histogramquantile(0.95, rate(kycverificationdurationseconds_bucket[5m])) > 8 for: 3m labels: severity: warning annotations: summary: "Latencia p95 supera el objetivo de 8 segundos" ``

  1. Validar la configuracion con amtool antes de desplegar:

``bash amtool check-config alertmanager.yml amtool config routes show --config.file=alertmanager.yml ``

Notes

  • Alertmanager debe desplegarse en modo cluster (minimo 2 instancias) en produccion para alta disponibilidad, usando el flag --cluster.peer para sincronizacion.
  • Los secrets de PagerDuty y Slack deben gestionarse mediante Kubernetes Secrets o un vault, nunca en texto plano en la configuracion.
  • El grupo de alertas por module permite correlacionar problemas con etapas especificas del pipeline KYC (liveness, facematch, ocr, docprocessing) y escalar al equipo correcto.