add-httpcheck-alert

Create SigNoz HTTP health check alerts for Kubernetes services via ArgoCD overlays.

5|Updated Aug 26, 2024

Search Tags:#monitoring #kubernetes #alerts #configmap #argo-cd #httpcheck #signoz

Ready to run

npx skills add https://github.com/jomcgi/homelab --skill add-httpcheck-alert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-httpcheck-alert
Source: https://github.com/jomcgi/homelab/tree/main/.claude/skills/add-httpcheck-alert
Command: npx skills add https://github.com/jomcgi/homelab --skill add-httpcheck-alert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create SigNoz HTTP health check alerts for services to monitor uptime and trigger notifications when health checks fail.

Core Features & Use Cases

Automatically generate ConfigMaps and overlay alerts for new services.
Integrate with ArgoCD deployment flow to ensure alerts are applied to production overlays.
Use case: Onboarding a new service, you can generate the required httpcheck-alert manifest and ensure it is picked up by the GitOps workflow.

Quick Start

Create and apply an HTTP health check alert for a new service using the add-httpcheck-alert command.

Frequently Asked Questions about add-httpcheck-alert

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

FAQPage Schema

How do I create SigNoz HTTP health check alerts for new Kubernetes services?▼

To create SigNoz HTTP health check alerts, you need to generate ConfigMaps and overlay alerts using a service URL and namespace. This updates Kubernetes overlays and kustomizations to ensure proper monitoring through your GitOps workflow.

How do I automate health check alert creation with ArgoCD synchronization?▼

Automating health check alert creation with ArgoCD involves generating httpcheck-alert manifests and applying them to production overlays. This ensures the alerts are picked up by the ArgoCD synchronization workflow during service onboarding.

What is needed to set up HTTP health monitoring for a service in Kubernetes?▼

Setting up HTTP health monitoring requires a service URL and a namespace, which defaults to the service name. You must update Kubernetes overlays and kustomizations to integrate the httpcheck-alert manifest into your deployment configuration.

Can I apply HTTP health check alerts to existing services using Kubernetes overlays?▼

Yes, you can apply HTTP health check alerts to existing services by updating production overlays and kustomizations. The process generates the required httpcheck-alert manifest and integrates it with your existing ArgoCD synchronization flow.

Does this alert generation process work with both new onboarding and production updates?▼

Yes, the alert generation process applies to both onboarding new services and updating production overlays. It automates the creation of required manifests and updates kustomizations to ensure monitoring is enabled across different deployment stages.

Why are my generated HTTP health check alerts not triggering in SigNoz?▼

HTTP health check alerts may not trigger if the Kubernetes overlays and kustomizations are not properly updated. You must ensure the generated ConfigMaps are correctly applied to production overlays and synchronized via ArgoCD for SigNoz to receive the monitoring data.