skills.rest
MapleTechLabs
MapleTechLabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

maple-onboard

Automate OpenTelemetry instrumentation of runnable services in a repository.

1.6k|107|Updated Feb 15, 2026
Search Tags:#observability#opentelemetry#maple#repo onboarding#service instrumentation#otel setup#telemetry configuration
One-click install
npx skills add https://github.com/MapleTechLabs/maple --skill maple-onboard-mapletechlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maple-onboard
Source: https://github.com/MapleTechLabs/maple/tree/main/skills/maple-onboard
Command: npx skills add https://github.com/MapleTechLabs/maple --skill maple-onboard-mapletechlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up OpenTelemetry traces, logs, and metrics across every service in a multi-app or monorepo codebase is time-consuming, requires deep knowledge of OTel for every tech stack, and often misses critical services like workers, mobile apps, or serverless functions. This skill eliminates that manual work by automatically instrumenting every runnable service in your repository for Maple observability.

Core Features & Use Cases

  • Full-repo instrumentation: Automatically detects and instruments every app, API, worker, mobile app, and serverless function in your repo, skipping only pure type/config packages with no runtime entry point.
  • Stack-native OTel setup: Uses the official OpenTelemetry SDK for each service's tech stack (Next.js, Node.js, Python, Effect-TS, Go, Rust, etc.) to avoid fragile custom wrappers, and follows framework-specific best practices for bootstrap order and configuration.
  • Vendor coexistence: Leaves existing observability tools like Sentry, Datadog, or New Relic intact, so you can run both OTel and your incumbent vendor side-by-side during migration.
  • Use case: For a monorepo with a Next.js storefront, Node.js order API, Python background worker, and Expo mobile app, this skill will add OTel instrumentation to all four services, configure the Maple ingest endpoint, add custom spans for order processing and payment flows, and set up structured logs with trace context.

Quick Start

Use this skill to automatically instrument every service in your repository with OpenTelemetry traces, logs, and metrics for full Maple observability coverage.

Frequently Asked Questions about maple-onboard

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

FAQPage Schema
How do I set up OpenTelemetry instrumentation for multiple services in a monorepo?▼

OpenTelemetry instrumentation for multiple services in a monorepo is automated by detecting every runnable application and applying stack-specific OTel SDK bootstrapping for traces, logs, and metrics. This eliminates manual setup across mixed tech stacks like Next.js, Python, and Go.

Can I configure Maple observability without removing my existing Datadog or Sentry instrumentation?▼

Maple observability supports vendor coexistence, allowing you to run OpenTelemetry side-by-side with existing observability tools like Datadog or Sentry. The instrumentation process leaves incumbent vendors intact during your migration.

What is the best way to add OpenTelemetry traces to an Expo mobile app and Cloudflare Workers?▼

Adding OpenTelemetry traces to an Expo mobile app and Cloudflare Workers is handled automatically by detecting the runtime environments and applying framework-specific OTel bootstrap configurations. This ensures proper telemetry egress without fragile custom wrappers.

Does repo onboarding for observability support Go, Rust, and Java tech stacks?▼

Repo onboarding for observability supports Go, Rust, Java, C#, and Kotlin alongside Node.js and Python. It uses the official OpenTelemetry SDK for each specific tech stack to ensure proper semantic convention-compliant resource attributes.

How do I test OpenTelemetry telemetry egress after instrumenting my repository?▼

Testing OpenTelemetry telemetry egress is accomplished through an automated end-to-end smoke test included in the onboarding process. This verifies that traces, logs, and metrics are correctly configured to reach the Maple ingest endpoint.

How do I configure the Maple ingest endpoint and API key for OpenTelemetry?▼

Configuring the Maple ingest endpoint and API key for OpenTelemetry is handled inline during the automated instrumentation setup. The process applies write-only API key configurations to ensure secure telemetry data export.

Related Skills

Explore More Software Engineering Skills→
BagelHoleBagelHole
46

opentelemetry

Instrument applications and infrastructure with OpenTelemetry for unified traces, metrics, and logs.

Community
Intermediate
MakisuoMakisuo
1.6k

maple-java-style

Instrument Java applications for Maple observability via OpenTelemetry agent or SDK.

Community
Advanced
spreespree
4

spree-dependencies

Replace core Spree services with custom dependency-injected implementations.

Official
Advanced
MapleTechLabsMapleTechLabs
1.6k

maple-java-style

Configure Java applications to export OpenTelemetry traces, logs, and metrics to Maple.

Official
Intermediate