What problem does it solve? Engineers modifying the clawker monitoring stack risk breaking dashboards, metric labels, and log indices because the OpenTelemetry collector, Prometheus exporter, and OpenSearch ingest pipelines have non-obvious contracts (such as the type to kind label rewrite) that are easy to violate unknowingly. ## Core Features & Use Cases - Schema Reference: Complete field tables for Claude Code OTLP events (tool_result, api_request, api_error, user_prompt) and eBPF egress events, including OpenSearch index mappings and resource attribute paths. - Label Rewrite Documentation: Explains the Prometheus type to kind label rename workaround for the OpenSearch SQL direct-query bug, with removal criteria when the pinned image is bumped. - Verification Workflow: A four-step procedure for validating template, datasource, workspace, and saved-object changes, including the mandatory monitor down --volumes rebuild cycle. - Use Case: After editing otel-config.yaml.tmpl, follow the workflow to rebuild the binary, re-bootstrap the stack with volumes wiped, and confirm saved objects land in the Clawker workspace at localhost:5601. ## Quick Start Use the monitoring-checks skill to verify my changes to the OpenSearch dashboard saved objects and confirm the Prometheus metric labels still resolve correctly.