Monitoring

This skill sets up log aggregation solutions using ELK (Elasticsearch, Logstash, Kibana), Loki, or Splunk. It generates production-ready configurations and setup code based on specific requirements and infrastructure. Use this skill when the user requests to set up logging infrastructure, configure log aggregation, deploy ELK stack, deploy Loki, deploy Splunk, or needs help with observability. It is triggered by terms like "log aggregation," "ELK setup," "Loki configuration," "Splunk deployment," or similar requests for centralized logging solutions.

This skill enables Claude to create intelligent alerting rules for proactive performance monitoring. It is triggered when the user requests to "create alerts", "define monitoring rules", or "set up alerting". The skill helps define thresholds, routing, and escalation policies, and offers options for multi-category alert creation, including latency, error rate, throughput, resource utilization, availability, and SLO violation alerts. It is useful for Site Reliability Engineers (SREs) and DevOps teams looking to improve system observability.

現代的なSREプラクティスに基づくObservabilityと監視システム設計の専門知識。メトリクス、ログ、トレースの3本柱とダッシュボード設計、SLI/SLO定義を提供。Anchors:• Google SRE Book / 適用: Observabilityアーキテクチャ・SLI/SLO設計 / 目的: 本番環境対応の監視システム• Observability Engineering (Honeycomb) / 適用: モダンObservabilityパターン / 目的: 高カーディナリティObservability実装• The Art of Monitoring (James Turnbull) / 適用: 実践的な監視実装 / 目的: エンドツーエンドの監視ワークフローTrigger:Use when designing observability systems, implementing metrics collection, setting up distributed tracing, creating dashboards, defining SLIs/SLOs, or establishing logging strategies.observability, monitoring, metrics, traces, logs, SLI, SLO, Prometheus, Grafana, OpenTelemetry

分散トレーシングの設計とOpenTelemetry導入を支援するスキル。トレース構造、スパン設計、検証手順を体系化する。Anchors:• Observability Engineering / 適用: 観測設計 / 目的: 可観測性の一貫性確保• W3C Trace Context / 適用: コンテキスト伝播 / 目的: 標準準拠• OpenTelemetry / 適用: 計測とエクスポート / 目的: ベンダー非依存化Trigger:Use when designing trace structures, implementing OpenTelemetry instrumentation, or validating span propagation.distributed tracing, opentelemetry, span, trace context, w3c

This skill automates the setup of distributed tracing for microservices. It helps developers implement end-to-end request visibility by configuring context propagation, span creation, trace collection, and analysis. Use this skill when the user requests to set up distributed tracing, implement observability, or troubleshoot performance issues in a microservices architecture. The skill is triggered by phrases such as "setup tracing", "implement distributed tracing", "configure opentelemetry", or "add observability to microservices".

This skill automates the setup of distributed tracing for microservices. It helps developers implement end-to-end request visibility by configuring context propagation, span creation, trace collection, and analysis. Use this skill when the user requests to set up distributed tracing, implement observability, or troubleshoot performance issues in a microservices architecture. The skill is triggered by phrases such as "setup tracing", "implement distributed tracing", "configure opentelemetry", or "add observability to microservices".

This skill deploys monitoring stacks, including Prometheus, Grafana, and Datadog. It is used when the user needs to set up or configure monitoring infrastructure for applications or systems. The skill generates production-ready configurations, implements best practices, and supports multi-platform deployments. Use this when the user explicitly requests to deploy a monitoring stack, or mentions Prometheus, Grafana, or Datadog in the context of infrastructure setup.

Chokidarライブラリを中心としたファイルシステム監視の専門スキル。Observer Patternによる効率的なファイル変更検知、クロスプラットフォーム対応、EventEmitterによる疎結合な通知システムを設計・実装する。Anchors:• Node.js EventEmitter / 適用: イベント駆動設計 / 目的: 疎結合な通知メカニズム• Chokidar Documentation / 適用: ファイル監視設定 / 目的: クロスプラットフォーム監視• Observer Pattern (GoF) / 適用: イベント通知設計 / 目的: 変更検知と通知の分離Trigger:Use when implementing file system watching, Chokidar configuration, file change detection, or event-based file monitoring systems.file watching, chokidar, fs watch, file change, event emitter, observer pattern, hot reload

Implement monitoring, alerting, and observability with CloudWatch

Configure OpenTelemetry tracing, metrics, and structured logging for DAPR applications. Integrates with Azure Monitor, Jaeger, Prometheus, and other observability backends.

Enforces Head Shakers server-side Sentry monitoring conventions when implementing error tracking, performance monitoring, and breadcrumb logging in server actions, facades, middleware, and API routes. This skill ensures consistent patterns for context setting, breadcrumb categories, error capture, and performance spans.

Spring Boot 4 observability with Actuator, Micrometer, and OpenTelemetry. Use when configuring health indicators, custom metrics, distributed tracing, production endpoint exposure, or Kubernetes/Cloud Run probes. Covers Actuator security, Micrometer Timer/Counter/Gauge patterns, and OpenTelemetry span customization.

Implement observability solutions. Use when setting up monitoring, logging, or tracing. Covers OpenTelemetry, metrics, and alerting.

Testing in production with feature flags, canary deployments, synthetic monitoring, and chaos engineering. Use when implementing production observability or progressive delivery.

Production observability with tracing, OpenTelemetry, and Prometheus metrics including structured logging, instrumented functions, distributed tracing, health checks, and request correlation. Use when adding logging, metrics, tracing, or health endpoints to Rust services.

Game server monitoring with metrics, alerting, and performance tracking for production reliability

OpenTelemetry observability - use for distributed tracing, metrics, instrumentation, Sentry integration, and monitoring

Production monitoring, observability, SLO/SLI management, and incident response.Trigger terms: monitoring, observability, SRE, site reliability, alerting, incident response,SLO, SLI, error budget, Prometheus, Grafana, Datadog, New Relic, ELK stack, logs, metrics,traces, on-call, production monitoring, health checks, uptime, availability, dashboards,post-mortem, incident management, runbook.Completes SDD Stage 8 (Monitoring) with comprehensive production observability:- SLI/SLO definitions and tracking- Monitoring stack setup (Prometheus, Grafana, ELK, Datadog, etc.)- Alert rules and notification channels- Incident response runbooks- Observability dashboards (logs, metrics, traces)- Post-mortem templates and analysis- Health check endpoints- Error budget trackingUse when: user needs production monitoring, observability platform, alerting, SLOs,incident response, or post-deployment health tracking.

This skill should be used when adding error tracking and performance monitoring with Sentry and OpenTelemetry tracing to Next.js applications. Apply when setting up error monitoring, configuring tracing for Server Actions and routes, implementing logging wrappers, adding performance instrumentation, or establishing observability for debugging production issues.

SQL Server administration and maintenance. Use for database backups, security, user management, maintenance tasks, monitoring, and troubleshooting.