Use when implementing observability for Microsoft Agent Framework agents. Triggers: "agent observability", "OpenTelemetry agents", "agent metrics", "agent tracing", "Aspire dashboard". NOT for: Non-Microsoft agent frameworks or basic logging.
Investigate platform incidents, perform RCA, create incident documentation, and follow alert runbooks in the Kagenti platform
Query and analyze logs using Grafana Loki for the Kagenti platform, search for errors, and investigate issues
DevOps Monitor Agent. 시스템 모니터링, 로그 분석, 상태 확인을 담당합니다. 모니터링, 상태(status), 로그(logs), 알림 관련 요청 시 사용됩니다.
Use when building distributed apps with Aspire; orchestrating .NET, JavaScript, Python, or polyglot services; when environment variables or service discovery aren't working; when migrating from .NET Aspire 9 to 13+ or Community Toolkit; when seeing AddNpmApp deprecated errors; when OTEL not appearing in dashboard; when ports change on restart breaking OAuth; when configuring MCP server for AI assistants; when debugging Aspire apps and need to check resource status or logs
Use when debugging errors with Sentry context, investigating production issues, triaging Sentry alerts, or when user mentions "sentry", "error tracking", "production error", or "investigate issue"
Monitoring and observability tools including Prometheus, OpenTelemetry, and Netdata
Expert in ELK stack management, optimization, and deployment. Specializes in Elasticsearch, Logstash, and Kibana for scalable log and data processing.
Managing instance actor orchestrations for PostgreSQL health monitoring. Use when debugging stale actors, restarting actors, or troubleshooting health check issues.
Instrument API requests with spans and distributed tracing. Use when tracking request latency or debugging API issues.
Monitor message queues, job processing, and detect backpressure
Datadogでサービス状態を調査。「Datadogで調べて」「サービスの状態確認」「エラー調査」等で起動。
Implement comprehensive audit logging for all admin actions, capturing user ID, action type, entity changes, IP address, and user agent. Use when tracking system activities or adding audit trails.
Structured JSON logging with correlation IDs for multi-service systems. Use when implementing logging, debugging failures, or tracing errors across services. Triggers on: add logging, error handling, debug failures, trace errors.
Configures logging systems, log aggregation, and log analysis pipelines
Converts Grafana dashboard JSON exports to Jsonnet using grafana-code mixin conventions. Use when importing dashboards from Grafana UI exports, migrating to infrastructure-as-code, or integrating JSON dashboards into grafana-code. Produces self-contained Jsonnet files with unified libraries, modernizes legacy panel types, and supports manual import with datasource selection.
Self-Improving Agent that monitors all other agent skills, analyzes their logs, detects issues, and proposes improvements. AUTO-TRIGGERS: - Every 30 minutes (scheduled) - When error rate > 5% (any agent) - When 3+ recurring errors in 24h (same error type) - When performance degrades > 2x baseline
Instrument a webapp to send useful telemetry data to Azure App Insights
Aggregation phase for /health-check command - produces final report
Replaces Phoenix observability with Langfuse Cloud (EU) traceability for pharmaceutical test generation. Adds @observe decorators to existing code, configures LlamaIndex callbacks, propagates GAMP-5 compliance attributes, and removes Phoenix dependencies. Use PROACTIVELY when implementing Task 2.3 (LangFuse setup), migrating observability systems, or ensuring ALCOA+ trace attribution. MUST BE USED for pharmaceutical compliance monitoring requiring persistent cloud storage.
Trace production alerts and issues back through REQ-* to original intent, creating new intent for remediation. Closes feedback loop from Runtime → Intent. Use when production alerts fire or issues discovered.
Set up structured logging, metrics, and monitoring dashboards. Use when adding logging, setting up alerts, debugging production issues, or implementing analytics.
Manage PrismaClient lifecycle with graceful shutdown, proper disconnect timing, and logging configuration. Use when setting up application shutdown handlers, configuring logging for development or production, or implementing proper connection cleanup in Node.js servers, serverless functions, or test suites.
