maple-java-style

Configure Java applications to export OpenTelemetry 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-java-style-mapletechlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maple-java-style
Source: https://github.com/MapleTechLabs/maple/tree/main/skills/maple-java-style
Command: npx skills add https://github.com/MapleTechLabs/maple --skill maple-java-style-mapletechlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the complex, time-consuming work of manually instrumenting Java applications to send observability data (traces, logs, metrics) to Maple's OpenTelemetry-based backend, removing the need for extensive custom code for standard framework instrumentation.

Core Features & Use Cases

  • Zero-code auto-instrumentation: Uses the OpenTelemetry Java Agent to automatically instrument common Java frameworks including Spring Boot, JDBC, Kafka, and gRPC with no application code changes required.
  • Manual SDK implementation: Provides guidance for edge cases where the agent cannot run, such as GraalVM native images or sealed module paths, with full control over span creation and configuration.
  • Log context bridging: Configures existing Logback/SLF4J logging setups to carry trace and span context, so logs are correlated with traces in Maple.
  • Use Case: A Java backend team running an orders API can deploy the OpenTelemetry Java Agent with inline Maple endpoint and ingest key configuration to start sending full observability data to Maple in minutes, or use manual instrumentation to add custom business spans for order submission workflows.

Quick Start

Use the maple-java-style skill to configure your Java application to send OpenTelemetry traces, logs, and metrics to your Maple ingest endpoint using either the zero-code Java agent or manual SDK setup based on your runtime requirements.

Frequently Asked Questions about maple-java-style

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

FAQPage Schema
How do I send OpenTelemetry traces and logs from a Java application to Maple?

To send OpenTelemetry traces and logs to Maple, configure your Java application using the OpenTelemetry Java Agent for zero-code auto-instrumentation or implement the manual SDK to export telemetry data via OTLP HTTP to your Maple ingest endpoint.

Can I use zero-code Java auto-instrumentation for Spring Boot and Kafka with Maple?

Yes, zero-code Java auto-instrumentation supports common frameworks like Spring Boot, JDBC, Kafka, and gRPC by attaching the OpenTelemetry Java Agent to automatically collect traces, logs, and metrics without modifying application code.

How do I correlate Logback logs with OpenTelemetry traces in Maple?

To correlate Logback logs with OpenTelemetry traces, configure log context bridging in your SLF4J logging setup to carry trace and span context, ensuring logs are correlated with traces in the Maple observability backend.

Does the OpenTelemetry Java agent work with GraalVM native images?

No, the OpenTelemetry Java agent does not work with GraalVM native images, so you must use manual SDK implementation to control span creation and configure OTLP HTTP export for observability data in these edge cases.

What is the best way to configure OpenTelemetry endpoint and ingest keys for a Java app?

The best way to configure OpenTelemetry endpoints and ingest keys is through inline configuration when deploying the Java agent or manual SDK, enabling rapid setup to export traces, logs, and metrics to the Maple backend.