maple-go-style

Configures OpenTelemetry instrumentation for Go applications to send traces, logs, and metrics to Maple.

1.6k|107|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/MapleTechLabs/maple --skill maple-go-style-mapletechlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maple-go-style
Source: https://github.com/MapleTechLabs/maple/tree/main/skills/maple-go-style
Command: npx skills add https://github.com/MapleTechLabs/maple --skill maple-go-style-mapletechlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about maple-go-style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up OpenTelemetry instrumentation in Go to send traces and metrics to Maple?

Set up OpenTelemetry instrumentation in Go by using pre-configured SDK bootstrap code that initializes HTTP exporters for traces, logs, and metrics with Maple's ingest endpoint and required resource attributes.

What resource attributes are required for Go telemetry data sent to the Maple observability platform?

Required resource attributes for Maple telemetry include standardized semantic conventions and VCS metadata attributes, ensuring consistent telemetry attribution across all Go services sending data to the observability platform.

Can I use Maple OpenTelemetry instrumentation alongside existing observability backends like Honeycomb or Datadog?

Yes, Maple OpenTelemetry instrumentation supports coexistence with existing observability backends like Honeycomb or Datadog, allowing your Go services to export telemetry data to multiple platforms without configuration conflicts.

What's the best way to manage span lifecycle and errors in Go OpenTelemetry for production?

Manage span lifecycle in production Go applications by implementing bounded business spans and proper span error handling, preventing unhandled span errors and ensuring consistent trace data export to your observability backend.

How do I configure OpenTelemetry HTTP exporters for a Go service targeting Maple?

Configure OpenTelemetry HTTP exporters for a Go service by applying pre-initialized SDK code that includes inline endpoint and ingest key configuration, automatically routing trace, log, and metric data to Maple.