monitoring-expert

Configure structured logging, Prometheus metrics, alerting, and OpenTelemetry tracing for AI services.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill monitoring-expert-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-expert
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/claude-skills/skills/monitoring-expert
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill monitoring-expert-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of limited visibility into production systems by guiding you to implement complete monitoring, structured logging, metrics, alerting, and distributed tracing.

Core Features & Use Cases

  • Structured logging pipelines: standardize JSON logging and correlation identifiers so production incidents can be diagnosed faster.
  • Prometheus metrics and dashboards: instrument application and infrastructure metrics and visualize them using RED/USE approaches.
  • Alerting and performance validation: define actionable Prometheus alerts and run load testing and profiling to verify the system behaves within targets.

Quick Start

Use the monitoring-expert skill to instrument your service with structured logs, Prometheus metrics, OpenTelemetry tracing, and Prometheus alert rules, then validate them with a k6 load test and profiling.

Frequently Asked Questions about monitoring-expert

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

FAQPage Schema
How do I set up observability for AI-enabled services using structured logging and distributed tracing?

Observability for AI-enabled services is set up by configuring structured JSON logs with correlation IDs, OpenTelemetry span instrumentation, and Prometheus metrics to diagnose production issues across logs, metrics, and traces.

What is the best way to configure Prometheus metrics and Grafana dashboards for application monitoring?

Configuring Prometheus metrics and Grafana dashboards involves instrumenting application counters and histograms, then visualizing them using RED and USE approaches to monitor application and infrastructure performance effectively.

How do I define actionable alerting rules in Prometheus to catch production incidents?

Actionable alerting rules in Prometheus are defined by setting specific alert thresholds on collected metrics, enabling you to catch and respond to production incidents based on quantified system behavior.

Can I use this monitoring setup to validate performance using load testing and application profiling?

Yes, you can validate performance using load testing and application profiling by running k6 load tests against your instrumented service to verify the system behaves within your defined performance targets.

Do I need OpenTelemetry to implement distributed tracing for diagnosing production issues?

OpenTelemetry is required to implement distributed tracing, providing span instrumentation that correlates requests across services to diagnose production issues effectively.

Why do structured logs need correlation IDs when setting up observability pipelines?

Structured logs need correlation IDs to standardize JSON logging pipelines, allowing production incidents to be diagnosed faster by tracing specific requests across distributed system components.