What problem does it solve?
Kotlin JVM services require correct OpenTelemetry instrumentation to send traces, logs, and metrics to Maple, but teams often struggle with choosing between zero-code agent and manual SDK setup, configuring OTLP exporters with the correct Maple ingest endpoints and authentication, and ensuring logs are properly bridged without disrupting existing logging frameworks.
Core Features & Use Cases
- Zero-code Java agent setup: Auto-instruments Spring Boot, Ktor, and popular JVM libraries with minimal configuration for fast observability deployment.
- Manual SDK configuration: Provides step-by-step guidance for native-image or sealed-module Kotlin builds that cannot use the Java agent.
- Log and metric bridging: Includes instructions for connecting existing Logback, SLF4J, and Log4j2 logging setups to send log data with trace context to Maple.
- APM coexistence: Supports running alongside existing Datadog, New Relic, or Honeycomb setups without conflict.
- Use Case: A team building a Ktor order processing API can use this skill to quickly instrument their service to send full trace, log, and metric data to Maple without rewriting their existing logging or monitoring infrastructure.
Quick Start
Use the maple-kotlin-style skill to configure OpenTelemetry observability for your Kotlin Ktor or Spring Boot service to send traces, logs, and metrics directly to Maple.