maple-java-style

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Java applications often struggle to gain observability without invasive changes. This skill provides a dual path to instrument Java apps for Maple observability: a zero-code OpenTelemetry Java Agent and a manual SDK approach with OTLP exporters and inline endpoint configuration.

Core Features & Use Cases

  • Zero-code Instrumentation: Auto-instrument Java apps with the OpenTelemetry Java Agent.
  • Manual SDK Option: Use a manual SDK with OTLP exporters when agent usage isn't possible; supports inline endpoint and ingest key, and semconv resource attributes.
  • Use Case: Instrument a Spring Boot service to export traces, metrics, and logs to Maple ingest using an inline endpoint and a configured repository URL.

Quick Start

Instrument a Java application by attaching the OpenTelemetry Java Agent and pointing the exporter to your Maple ingest endpoint, or integrate the OpenTelemetry SDK inline with your app.

Frequently Asked Questions about maple-java-style

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

FAQPage Schema
How do I instrument a Java application for OpenTelemetry without changing code?

You can instrument Java applications without code changes by attaching the OpenTelemetry Java Agent, which automatically exports traces, metrics, and logs to your configured Maple ingest endpoint.

How do I configure OTLP exporters for a Java app manually?

You can manually configure the OpenTelemetry SDK with OTLP exporters by providing an inline endpoint, an ingest key, and semconv resource attributes to propagate Maple telemetry from your Java application.

What is the difference between zero-code Java agent instrumentation and the manual SDK approach?

The zero-code Java agent automatically instruments your application, while the manual SDK approach requires inline integration to configure OTLP exporters when agent attachment is not possible in your environment.

How do I send traces, metrics, and logs to a Maple ingest endpoint from Spring Boot?

To send telemetry to Maple ingest from a Spring Boot service, configure the OpenTelemetry Java Agent or manual SDK with your inline endpoint, ingest key, and a configured repository URL to export data.

When should I use the manual OpenTelemetry SDK instead of the Java agent for observability?

You should use the manual OpenTelemetry SDK instead of the Java agent when agent usage is not possible in your deployment environment, allowing you to inline configure OTLP exporters for traces, metrics, and logs.