Help us improve
Share bugs, ideas, or general feedback.
From vanguard-frontier-agentic
Reviews OpenTelemetry Collector configurations managed by the Operator for pipeline correctness, deployment mode, memory safety, sampling integrity, and auto-instrumentation coverage.
npx claudepluginhub raishin/vanguard-frontier-agentic --plugin vanguard-frontier-agenticHow this skill is triggered — by the user, by Claude, or both
Slash command
/vanguard-frontier-agentic:opentelemetry-collector-config-reviewThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review OpenTelemetry Operator-managed `OpenTelemetryCollector` and `Instrumentation` resources against pipeline correctness, deployment-mode appropriateness, memory safety, sampling integrity, exporter security, and Kubernetes-attribute enrichment. Telemetry pipelines fail silently — a misconfigured exporter drops every span; a missing `memory_limiter` OOMs the collector; a deleted `Instrumenta...
Configures and deploys the OpenTelemetry Collector: receivers, exporters, processors, pipelines, sampling, RED metrics, and custom distributions. Use for agent/gateway patterns, Kubernetes (operator, Helm chart, raw manifests), and Dash0 forwarding.
Authors, reviews, and debugs OpenTelemetry Collector YAML configuration for receivers, processors, exporters, connectors, and extensions. Covers config keys, defaults, validation, and stability levels.
Instrument apps with OpenTelemetry and send telemetry to Grafana Cloud via OTLP. Covers SDK setup, Alloy collector, sampling, and migration from other observability tools.
Share bugs, ideas, or general feedback.
Review OpenTelemetry Operator-managed OpenTelemetryCollector and Instrumentation resources against pipeline correctness, deployment-mode appropriateness, memory safety, sampling integrity, exporter security, and Kubernetes-attribute enrichment. Telemetry pipelines fail silently — a misconfigured exporter drops every span; a missing memory_limiter OOMs the collector; a deleted Instrumentation resource stops auto-instrumentation on next pod restart.
kubectl get opentelemetrycollectors,instrumentations -A -o yaml plus collector logs and metrics) when the active client exposes it; otherwise fall back to official OpenTelemetry documentation (opentelemetry.io, opentelemetry-operator) and sanitized YAML.Instrumentation propagation was not queried, say so.debug exporter in production) as a critical finding — telemetry is dropped at the collector.memory_limiter processor as a critical finding — collector OOMs and loses spans/metrics on burst traffic.k8sattributes processor as a high finding — telemetry loses k8s.namespace.name, k8s.pod.name, k8s.deployment.name, and SLO dashboards lose context.Instrumentation CR removal in a running namespace — auto-instrumented pods stop emitting telemetry after their next restart.tls.insecure: true in production — telemetry data flows in plaintext, often containing PII/PHI.Load these only when needed:
Return, at minimum:
OpenTelemetryCollector of which mode, Instrumentation CR, or pipeline element) and evidence level,