Set up Prometheus, Grafana, Loki, and Jaeger for Kubernetes observability.
npx skills add https://github.com/timequity/plugins --skill monitoring-setup
Please help me install this Agent Skill. Skill: monitoring-setup Source: https://github.com/timequity/plugins/tree/main/craft-coder/infra/monitoring-setup Command: npx skills add https://github.com/timequity/plugins --skill monitoring-setup
This Skill helps you implement a complete observability stack with metrics, logs, and traces to monitor system health and performance.
Set up Prometheus scrape configs, deploy Grafana, and import a sample dashboard to start observing your services.
High-intent search queries and answers about installing and using this skill.
Prometheus scrapes metrics from your services on a configured interval, storing time-series data. Grafana visualizes those metrics through dashboards. Deploy Prometheus with scrape configs targeting your Kubernetes endpoints, then connect Grafana as a data source to begin building dashboards and alerting rules.
Log aggregation via Loki or ELK collects logs from distributed services into a central store. Distributed tracing with Jaeger or Tempo tracks requests across service boundaries. Together they provide the complete observability picture—logs for debugging, traces for understanding request flow—complementing Prometheus metrics.
Yes. Prometheus alert rules define thresholds and conditions, while Grafana consumes those alerts and renders dashboards. Grafana dashboards visualize metrics in real time, and alert notifications trigger based on Prometheus rule evaluations, creating an integrated monitoring and alerting workflow.
This stack is optimized for Kubernetes-based applications and cloud-native microservices. While Prometheus, Grafana, and Loki can run elsewhere, the Skill targets cloud-native environments where service discovery, container metrics, and distributed architectures benefit most from end-to-end observability.
Storage scales with metric cardinality and data retention policies; high-volume environments require careful scrape interval tuning. Loki indexing and Jaeger storage have capacity constraints. Alert rule complexity can cause notification fatigue if thresholds aren't calibrated. Plan retention and resources accordingly.
Prometheus scrape configs define which targets to collect metrics from and how often. Alert rules evaluate those metrics against conditions and fire alerts when thresholds are breached. Together they automate detection of system issues and provide the raw data that powers Grafana dashboards and notifications.
MakisuoInstrument Rust applications to export traces, metrics, and logs to Maple.
altrupetsAutomate alerting and incident management setup with Prometheus, Alertmanager, and PagerDuty.
jacexhInstrument Python applications with structured logging, Prometheus metrics, and OpenTelemetry tracing.
weirdgmeInstrument distributed systems with OpenTelemetry and correlate logs, metrics, and traces.
