What problem does it solve?
This Skill eliminates the risk of inconsistent or misconfigured OpenTelemetry instrumentation for Go applications sending telemetry to Maple, avoiding common errors like missing required resource attributes, incorrect exporter setup, or unhandled span lifecycle management.
Core Features & Use Cases
- Pre-configured SDK Bootstrap: Ready-to-use OpenTelemetry initialization code for traces, logs, and metrics with Maple's HTTP exporters, including inline endpoint and ingest key configuration.
- Standardized Resource Attributes: Enforces required semantic conventions and VCS metadata attributes for consistent telemetry attribution across services.
- Production Best Practices: Guidance for bounded business span implementation, auto-instrumentation of common Go libraries, and coexistence with existing observability backends like Honeycomb or Datadog.
- Use Case: A Go orders API team can use this Skill to quickly implement compliant telemetry that sends all trace, log, and metric data to Maple without manual SDK configuration or trial-and-error setup.
Quick Start
Use the maple-go-style skill to configure OpenTelemetry instrumentation for your Go application to send traces, logs, and metrics to Maple's ingest endpoint with correct resource attributes and proper span error handling.