monitor

Monitor running systems by collecting metrics, logs, dashboards, and health indicators.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill monitor-kord96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor
Source: https://github.com/Kord96/kordinate/tree/main/agents/sauron/skills/monitor
Command: npx skills add https://github.com/Kord96/kordinate --skill monitor-kord96

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Monitor a running system to collect and interpret observability signals across metrics, logs, dashboards, and health endpoints.

Core Features & Use Cases

  • Atlas-driven component selection aligns what to watch with architectural context.
  • Collects Prometheus metrics, Loki logs, Grafana dashboards, and health endpoints across components.
  • Optional integration with Augur Atlas and Charon config to tailor access and scope.
  • Use Case: quickly diagnose an outage by validating live signals against Atlas guidance and dashboards.

Quick Start

Provide a project name to initialize Atlas-driven monitoring for that project.

Frequently Asked Questions about monitor

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

FAQPage Schema
How do I collect Prometheus metrics and Loki logs for a running system?

To collect Prometheus metrics and Loki logs for a running system, specify a project name to initialize Atlas-driven monitoring, which automatically gathers and interprets observability signals across components.

What is Atlas-driven observability and how does it tailor what to monitor?

Atlas-driven observability aligns what to watch with your architectural context by using project and cluster definitions to select components, enforcing health checks and collecting relevant Grafana dashboards and metrics.

How do I diagnose an outage using Grafana dashboards and health checks?

Diagnose an outage by validating live signals against Atlas guidance and Grafana dashboards, applying enforced health checks across components to quickly identify and interpret failures within the running system.

Does monitoring work if Atlas or cluster access via Charon is unavailable?

Monitoring works if Atlas or Charon cluster access is unavailable because the system applies fallbacks to continue collecting metrics, logs, and health indicators without requiring full architectural context.

Can I validate monitoring specs against existing Prometheus and Loki configurations?

You can validate monitoring specs against existing configurations, as the system applies optional monitoring-spec validation alongside Prometheus and Loki signals to ensure observability coverage matches architectural intent.

What's the best way to enforce health checks across multiple cluster components?

The best way to enforce health checks across components is applying Atlas-driven monitoring to a project, which systematically collects health endpoints and validates live signals against defined cluster configurations.