observability

name	observability
description	Monitor and debug web applications using OpenTelemetry, console logs, network requests, and distributed tracing. Use when correlating frontend and backend requests or debugging request flow across services.

Observability Skill

Monitor and debug web applications using OpenTelemetry, console logs, network requests, and distributed tracing.

When to Use

This skill activates when:

• User asks about distributed tracing
• User wants to correlate frontend and backend requests
• User mentions OpenTelemetry, Jaeger, Zipkin, or tracing
• User needs to debug request flow across services
• User wants to monitor application behavior

Capabilities

Distributed Tracing

• Get current trace ID (o11y_get-trace-id)
• Generate new trace ID (o11y_new-trace-id)
• Set specific trace ID (o11y_set-trace-id)
• Correlate browser actions with backend traces

Console Monitoring

• Capture all console output (o11y_get-console-messages)
• Filter by level (error, warn, info, debug)
• Track JavaScript exceptions
• Monitor application logs

Network Observability

• Track HTTP requests (o11y_get-http-requests)
• Monitor API call timing
• Identify failed requests
• Inspect request/response details

Performance Metrics

• Core Web Vitals (o11y_get-web-vitals)
• Page load timing
• Resource timing
• User interaction metrics

OpenTelemetry Integration

Trace Context

Browser DevTools MCP can inject and extract W3C Trace Context headers: