Instrument Go codebases with OpenTelemetry traces, metrics, and logs.
npx skills add https://github.com/tsuga-dev/agent-plugins --skill otel-go-tsuga-dev
Please help me install this Agent Skill. Skill: otel-go Source: https://github.com/tsuga-dev/agent-plugins/tree/main/plugins/telemetry/skills/otel-go Command: npx skills add https://github.com/tsuga-dev/agent-plugins --skill otel-go-tsuga-dev
Correct OpenTelemetry (OTel) setup and instrumentation for Go services is hard because distributed tracing requires precise SDK initialization, context propagation, and signal-specific best practices to avoid missing data, broken correlations, or invalid span/metric semantics.
Use the otel-go skill when you need help adding or fixing OTel SDK setup or instrumentation in a confirmed Go service, and ask it to propose the minimal change plan before you apply any code updates.
High-intent search queries and answers about installing and using this skill.
To initialize the OpenTelemetry SDK in a Go service, configure the TracerProvider, MeterProvider, and LoggerProvider with correct resource attributes and propagation settings. This ensures traces, metrics, and logs are properly exported and correlated.
Propagate OpenTelemetry context across Kafka or RabbitMQ by implementing the producer/consumer model with span Links for consumer spans. This preserves accurate workflow boundaries in async messaging and prevents broken trace correlations.
Prevent sensitive data leaks in OpenTelemetry traces, logs, and metrics by following strict rules to avoid emitting credentials or PII into attributes. This ensures safe sensitive-data handling during instrumentation.
The best way to map HTTP status to OpenTelemetry span status in Go is to apply Go-specific span naming and status mapping rules. Correct context hygiene prevents orphan spans and misleading topology in distributed tracing.
Audit OpenTelemetry traces, metrics, and logs for cardinality issues by using a checklist-driven flow to verify presence, correlation, and naming quality. This cross-signal audit validates low-cardinality attributes across all signals.
OpenTelemetry instrumentation in Go requires explicit user confirmation before applying changes due to a mutation gate. The system proposes a minimal change plan and waits for approval before modifying the codebase.
raphaelmansuyEnable OpenTelemetry traces, metrics, and logs across AgentStack components.
FernanSuozaDesign observability plans for metrics, logs, traces, and alerts.
WbunkerProvides guidance on designing, testing, and deploying gRPC microservices with Kubernetes and Docker.
zach-sourceInstruments Python applications with OpenTelemetry for distributed tracing, metrics, and logging.
