moai-domain-monitoring

Collect metrics, logs, and traces from Kubernetes microservices using Prometheus, Grafana, Loki, OpenTelemetry, and Jaeger.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/jg-chalk-io/Nora-LiveKit --skill moai-domain-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-domain-monitoring
Source: https://github.com/jg-chalk-io/Nora-LiveKit/tree/main/.claude/skills/moai-domain-monitoring
Command: npx skills add https://github.com/jg-chalk-io/Nora-LiveKit --skill moai-domain-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full observability with metrics, logs, and traces to monitor production services.

Core Features & Use Cases

  • Metrics: Prometheus-based collection and dashboards.
  • Logs: Loki/ELK-style structured logging.
  • Traces: OpenTelemetry and Jaeger tracing across services.

Quick Start

Instrument a sample service with basic metrics, logs, and traces.

Frequently Asked Questions about moai-domain-monitoring

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

FAQPage Schema
How do I set up end-to-end observability for microservices in Kubernetes?

End-to-end observability combines metrics, logs, and traces across services. Use Prometheus for metrics collection, Loki for structured logging, OpenTelemetry for instrumentation, and Jaeger for distributed tracing. This Skill provides a complete stack with prebuilt Grafana dashboards to visualize all three signals together in Kubernetes environments.

What's the difference between Prometheus metrics, structured logs, and traces?

Prometheus metrics are time-series data (Counters, Gauges, Histograms) for system performance. Structured logs capture timestamped events with context in JSON format. Traces follow requests across microservices using Trace IDs and parent-child relationships. Together they provide complete visibility into production system behavior.

Can I use OpenTelemetry and Jaeger together for tracing microservices?

Yes. OpenTelemetry instruments your code to generate spans and traces with Trace IDs, while Jaeger exports and visualizes those traces. This Skill integrates both: OpenTelemetry collects instrumentation, Jaeger/Tempo backends store traces, and Grafana dashboards display results across your Kubernetes services.

How do I connect Prometheus alerting to my monitoring stack?

Prometheus Alertmanager integration triggers alerts based on metric thresholds. This Skill includes Alertmanager configuration alongside Prometheus collection and Grafana visualization, enabling automated notifications when production systems exceed defined alert conditions.

Do I need Loki if I already have structured JSON logging?

Loki indexes and queries structured JSON logs efficiently within your observability stack. While structured logging provides the format, Loki enables fast log retrieval, correlation with metrics and traces in Grafana, and reduces storage overhead compared to traditional log aggregators in Kubernetes environments.

What Prometheus metric types should I instrument for production services?

Use Counters for cumulative counts, Gauges for point-in-time values, and Histograms for request latency distribution. This Skill documents and demonstrates all three types with prebuilt Grafana dashboards that aggregate these metrics across microservices in Kubernetes for comprehensive production monitoring.