maple-nodejs-style

Configure OpenTelemetry NodeSDK to send traces, logs, and metrics to Maple via OTLP HTTP.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuring OpenTelemetry to send traces, logs, and metrics from Node.js applications to Maple requires manual setup of SDKs, exporters, and instrumentation, which is tedious and error-prone for teams working with different Node.js frameworks and runtimes.

Core Features & Use Cases

  • Pre-configured OpenTelemetry NodeSDK: Includes ready-to-use configuration for OTLP HTTP exporters tailored to Maple's ingest endpoints, eliminating boilerplate setup code.
  • Multi-Runtime & Framework Support: Works with Express, Fastify, Hono, and Bun, with out-of-the-box auto-instrumentation for common dependencies like HTTP clients, databases, and caches.
  • Non-Disruptive Integration: Provides best practices for bridging existing loggers (Pino, Winston) to carry trace context and coexisting with other APM tools (Sentry, Datadog) without replacing current workflows.
  • Use Case: A team building a Fastify API can use this skill to enable full observability in Maple in minutes, with automatic trace propagation and log correlation out of the box.

Quick Start

Use the maple-nodejs-style skill to configure OpenTelemetry for your Node.js application to send traces, logs, and metrics directly to your Maple ingest endpoint.

Frequently Asked Questions about maple-nodejs-style

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

FAQPage Schema
How do I configure OpenTelemetry for a Node.js app to send traces and metrics to Maple?

To configure OpenTelemetry for Node.js and send observability data to Maple, you can use a pre-configured NodeSDK setup with OTLP HTTP exporters. This eliminates manual SDK initialization and boilerplate code for Maple's ingest endpoints.

Does OpenTelemetry auto-instrumentation work with Fastify, Express, Hono, and Bun runtimes?

Yes, OpenTelemetry auto-instrumentation works with Express, Fastify, Hono, and Bun runtimes. It provides out-of-the-box instrumentation for common dependencies like HTTP clients, databases, and caches across these environments.

Can I keep using Pino or Winston loggers while sending OpenTelemetry traces to Maple?

Yes, you can keep using Pino or Winston loggers while sending OpenTelemetry data to Maple. The setup provides best practices for bridging existing loggers to carry trace context, ensuring non-disruptive integration and log correlation.

Does OpenTelemetry NodeSDK integration coexist with existing APM tools like Sentry or Datadog?

Yes, OpenTelemetry NodeSDK integration coexists with existing APM tools like Sentry or Datadog. It is designed for non-disruptive integration, allowing you to collect metrics and traces for Maple without replacing your current monitoring workflows.

What is the best way to enable distributed tracing and log correlation for a Node.js API on Maple?

The best way to enable distributed tracing and log correlation for a Node.js API on Maple is using a pre-configured OpenTelemetry NodeSDK. It automatically handles trace propagation and maps logs to traces via OTLP HTTP exporters.

Why does manual OpenTelemetry SDK setup fail to send Node.js observability data to Maple ingest endpoints?

Manual OpenTelemetry SDK setup often fails due to incorrect OTLP HTTP exporter configuration or missing authentication headers for Maple ingest endpoints. A pre-configured NodeSDK eliminates this tedious and error-prone manual configuration overhead.