Establish OpenTelemetry observability for HTTP, gRPC, and GraphQL instrumentation.
npx skills add https://github.com/pure-golang/level85 --skill x-observability
Please help me install this Agent Skill. Skill: x-observability Source: https://github.com/pure-golang/level85/tree/main/.agents/skills/x-observability Command: npx skills add https://github.com/pure-golang/level85 --skill x-observability
This Skill ensures consistent OpenTelemetry observability when you add new external operations, adapter packages, or server middleware, so traces and metrics are meaningful and middleware ordering doesn’t hide failures.
Add observability for your new adapter or middleware by wiring monitoring.InitDefault at the application bootstrap, creating a package tracer/meter with consistent span names, and placing HTTP monitoring outside recovery while keeping GraphQL as a child of the HTTP monitoring span.
High-intent search queries and answers about installing and using this skill.
To set up OpenTelemetry observability, initialize monitoring via monitoring.InitDefault at bootstrap, define one package-level tracer and meter, and apply consistent span naming like packageName.Operation for HTTP and gRPC operations.
OpenTelemetry monitoring middleware must be placed outside recovery middleware. This ordering ensures monitoring captures the full request lifecycle, preventing recovery handlers from hiding latency or error signals from traces.
To preserve parent-child trace relationships in GraphQL, ensure the GraphQL operation span is created as a child of the outer HTTP monitoring span. This maintains continuous trace context across transport and application layers.
No, telemetry and tracing failures must not block the application. Observability instrumentation should be handled safely so that errors in span creation or metrics recording do not interrupt the primary business logic.
Add spans and metrics to adapter packages only when they reflect real request, error, or latency signals. Avoid creating meaningless telemetry and never include sensitive data in span attributes to maintain security compliance.
FaysilAlshareefConfigure Serilog structured logging with enrichers and a Seq sink.
HZeroxiumImplement distributed tracing across microservices with OpenTelemetry and W3C Trace Context.
salvo-rsCapture request metrics, trace spans, and error contexts for Salvo routes.
adamhjkManage SolidJS reactive primitives for custom reactive workflows.
