monitoring

Run health checks and collect resource metrics across containers, Kubernetes, and services.

7|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill monitoring-brainbrewlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/brainbrewlabs/brainbrew-devkit/tree/main/plugin/config/templates/devops/skills/monitoring
Command: npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill monitoring-brainbrewlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and summarizes application health, resource strain, and service availability so teams can quickly understand system status after deployments or incidents.

Core Features & Use Cases

  • Health Checks Across Platforms: Run HTTP, Kubernetes, and Docker health checks to determine service availability.
  • Resource Monitoring: Collect CPU, memory, and disk metrics for containers, nodes, and hosts to spot capacity issues.
  • Log Sampling & Error Detection: Inspect recent logs to surface errors and correlate them with degraded or failing services.
  • Status Classification & Recommendations: Classify overall status as HEALTHY, DEGRADED, or DOWN and provide actionable remediation steps.

Quick Start

Use the monitoring skill to run platform-appropriate health checks, gather resource metrics, inspect recent logs, and produce a concise monitoring report.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I check Kubernetes cluster health and uptime after a deployment?

Verify Kubernetes cluster health and uptime after deployment by running HTTP health checks, sampling resource metrics, and inspecting recent logs to classify service status as HEALTHY, DEGRADED, or DOWN. You receive actionable remediation recommendations based on the detected errors and capacity issues.

What is the best way to monitor Docker container resource usage and detect errors?

Monitor Docker container resource usage by collecting CPU, memory, and disk metrics for nodes and hosts. You detect errors by inspecting recent container logs to surface issues, correlating them with degraded services, and generating a concise status report with remediation steps.

Can I use this to validate health endpoints and summarize service availability?

Validate health endpoints and summarize service availability by running platform-appropriate HTTP checks across containers and system services. The process provides endpoint validation, samples recent resource metrics, and outputs an overall status classification.

Does monitoring work without external dependencies or alerting tools?

Monitoring operates with no external dependencies, using standard platform APIs to gather metrics and logs. It samples resource data, inspects recent logs for errors, and produces a status report, functioning independently of dedicated alerting or metrics tools.

How do I inspect recent logs to find the cause of a degraded service?

Inspect recent logs to find the cause of a degraded service by sampling log outputs from containers, Kubernetes clusters, and system services. The process surfaces recent errors, correlates them with capacity issues, and provides actionable remediation recommendations.

When should I review resource usage metrics for containers and nodes?

Review resource usage metrics for containers and nodes during post-deployment checks or incident response to spot capacity issues. Sampling CPU, memory, and disk metrics helps identify resource strain and classify the overall system status as HEALTHY, DEGRADED, or DOWN.