Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

ankra-alerts-webhooks

Étoiles32

Forks2

Mis à jour7 juillet 2026 à 21:02

Configure alerting and notifications for Kubernetes clusters through Ankra - alert rules and outbound webhooks that notify Slack, Microsoft Teams, Discord, PagerDuty, Opsgenie, Datadog, or custom endpoints, with automatic AI incident analysis attached to alerts. Use when the user wants alerting, notifications, incident routing, or on-call integration for a Kubernetes cluster in an Ankra environment.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

ankraio

ankraio/ankra-cli

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Administrateurs de réseaux et de systèmes informatiquesProfessions informatiques et mathématiques·SOC 15-1244

SKILL.md

readonly

name

ankra-alerts-webhooks

description

Ankra Alerts & Webhooks

Ankra raises alerts on cluster conditions and delivers them to external systems via webhooks. Alerts can carry AI incident analysis so responders get context, not just a firing signal.

Webhook targets

ChatOps: Slack, Microsoft Teams, Discord.
On-call / incident: PagerDuty, Opsgenie.
Observability: Datadog.
Custom: any HTTPS endpoint that accepts a JSON POST.

Configure

Create a webhook pointing at the destination (channel webhook URL, PagerDuty/Opsgenie integration key, or custom endpoint). Store the URL/key as a credential, not in plaintext config.
Configure which alerts route to which webhook (severity, cluster, namespace scope).
Send a test event and confirm delivery in the destination.

AI incident analysis

When an alert fires, Ankra can attach an AI analysis of the likely cause and affected resources. Route high-severity alerts to your on-call tool (PagerDuty/Opsgenie) and informational ones to a ChatOps channel so the AI summary lands where responders look.

Rules

Secrets as credentials. Webhook URLs and integration keys are secrets - store them in Ankra credentials / the secret store, never commit them.
Scope and severity-route. Don't fan every alert to every channel; map severity to destination (critical → on-call, warning → chat).
Test delivery before relying on a route in production.
Avoid alert noise. Tune thresholds so alerts are actionable; noisy alerts get ignored.
Custom endpoints must be HTTPS and validate the payload.

Related skills

ankra-observability produces the signals that drive these alerts.
ankra-platform-principles for the secret-handling stance.

Plus depuis ce dépôt

même dépôt

ankra-cloud-clusters

ankraio/ankra-cli

Provision and manage Ankra-managed Kubernetes clusters (K3s or kubeadm) on Hetzner Cloud, OVHcloud, UpCloud, and DigitalOcean - creating clusters, storing provider credentials, and managing node groups, scaling, Kubernetes versions, and upgrades. Use when the user wants to create or provision a new Kubernetes cluster (rather than import an existing one), or mentions Hetzner, OVH, UpCloud, or DigitalOcean clusters.

2026-07-0932

ankra-cicd

ankraio/ankra-cli

Build CI/CD pipelines (GitHub Actions or GitLab CI) that deploy to Kubernetes the GitOps way - build a container image, push it with an immutable tag, and bump that tag in the Ankra GitOps repository so Ankra/ArgoCD syncs the change, rather than running kubectl/helm against the cluster from CI. Use when the user sets up CI/CD or automated deployment to a Kubernetes cluster in an Ankra environment, or asks how to deploy on push.

2026-07-0732

ankra-cli

ankraio/ankra-cli

Drive the Ankra CLI to log in, select an organisation and cluster, apply cluster/stack YAML, inspect pods, logs, events, and metrics, triage operations, and chat with Ankra AI. Use for day-to-day Kubernetes work whenever the `ankra` CLI is installed - checking what runs on a cluster, applying changes, debugging workloads, connecting kubectl - not only when the user names Ankra explicitly.

2026-07-0732

ankra-gitops

ankraio/ankra-cli

Structure a GitOps repository for Kubernetes with Ankra - modular include paths so cluster and stack definitions are stored in Git and synced by Ankra/ArgoCD. Use when the user sets up GitOps, connects a Git repository to a cluster, organizes cluster/stack YAML in a repo, or wants Git to be the source of truth for their Kubernetes configuration.

2026-07-0732

ankra-helm-registries

ankraio/ankra-cli

Connect HTTP and OCI Helm chart registries to Ankra and store least-privilege registry credentials (Harbor, Nexus, JFrog Artifactory, ChartMuseum, GHCR, Amazon ECR, Google Artifact Registry, Azure Container Registry, Docker Hub). Use when the user needs charts from a private registry on a Kubernetes cluster, or mentions Helm registries, OCI registries, or registry credentials.

2026-07-0732

ankra-import-cluster

ankraio/ankra-cli

Author and apply an Ankra ImportCluster YAML manifest that connects an existing Kubernetes cluster (EKS, GKE, AKS, k3s, on-prem, ...) to the Ankra platform, wires a GitOps repository, and declares stacks of manifests and Helm addons with dependency ordering. Use when the user wants to import, onboard, or connect an existing Kubernetes cluster to a management platform, write a cluster.yaml / ImportCluster file, or apply one with `ankra cluster apply`.

2026-07-0732

name

ankra-alerts-webhooks

description

Ankra Alerts & Webhooks

Ankra raises alerts on cluster conditions and delivers them to external systems via webhooks. Alerts can carry AI incident analysis so responders get context, not just a firing signal.

Webhook targets

ChatOps: Slack, Microsoft Teams, Discord.
On-call / incident: PagerDuty, Opsgenie.
Observability: Datadog.
Custom: any HTTPS endpoint that accepts a JSON POST.

Configure

Create a webhook pointing at the destination (channel webhook URL, PagerDuty/Opsgenie integration key, or custom endpoint). Store the URL/key as a credential, not in plaintext config.
Configure which alerts route to which webhook (severity, cluster, namespace scope).
Send a test event and confirm delivery in the destination.

AI incident analysis

Rules

Secrets as credentials. Webhook URLs and integration keys are secrets - store them in Ankra credentials / the secret store, never commit them.
Scope and severity-route. Don't fan every alert to every channel; map severity to destination (critical → on-call, warning → chat).
Test delivery before relying on a route in production.
Avoid alert noise. Tune thresholds so alerts are actionable; noisy alerts get ignored.
Custom endpoints must be HTTPS and validate the payload.

Related skills

ankra-observability produces the signals that drive these alerts.
ankra-platform-principles for the secret-handling stance.