maple-rust-style

Configure OpenTelemetry tracing, logs, and metrics for Rust services via OTLP HTTP to Maple.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual boilerplate and inconsistent configuration of OpenTelemetry observability for Rust services integrated with the Maple platform, ensuring all traces, logs, and metrics are correctly routed to Maple's ingest endpoints with minimal setup effort.

Core Features & Use Cases

  • Pre-configured OTLP HTTP Exporter: Ready-to-use setup for sending traces, logs, and metrics to Maple's ingest endpoint via HTTP, no manual exporter configuration required.
  • Tracing Crate Bridge: Native integration with the Rust tracing crate, so existing info!, error!, and #[tracing::instrument] calls automatically flow to Maple without code changes.
  • Standardized Resource Attributes: Pre-built resource attributes following OpenTelemetry semantic conventions for service name, deployment environment, and version control metadata to ensure consistent observability data.
  • Use Case: A Rust backend team building a microservice for Maple can use this Skill to add full observability in minutes, with all telemetry data automatically appearing in the Maple dashboard for monitoring and debugging.

Quick Start

Use the maple-rust-style skill to configure full OpenTelemetry tracing, logging, and metrics support for your Rust service that sends telemetry data to Maple.

Frequently Asked Questions about maple-rust-style

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

FAQPage Schema
How do I set up OpenTelemetry tracing in Rust to export telemetry via OTLP HTTP?

You can configure OpenTelemetry tracing in Rust by using a pre-configured OTLP HTTP exporter that sends traces, logs, and metrics directly to the Maple ingest endpoint without manual setup.

Can I use the Rust tracing crate with OpenTelemetry without changing my existing instrumentation?

Yes, native tracing crate bridge integration allows existing `info!`, `error!`, and `#[tracing::instrument]` calls to flow to Maple automatically, enabling OpenTelemetry export without code changes.

Do I need to manually configure semantic resource attributes for Rust OpenTelemetry metrics and logs?

No, standardized resource attributes following OpenTelemetry semantic conventions for service name, deployment environment, and version control metadata are pre-built to ensure consistent telemetry data.

Will adding OpenTelemetry exporters break my pre-existing tracing exporters in a Rust service?

No, the configuration supports coexistence with pre-existing tracing exporters, allowing you to add OTLP HTTP export to Maple alongside your current tracing setup without conflicts.

What is the best way to get Rust backend microservice observability data into a centralized dashboard?

The best way to achieve Rust microservice observability is applying standardized OpenTelemetry configuration that routes traces, logs, and metrics to the Maple dashboard for monitoring and debugging.

Do I need to add opentelemetry ecosystem dependencies manually for my Rust service?

No, the setup satisfies requirements for pre-configured opentelemetry ecosystem dependencies, eliminating manual boilerplate and ensuring correct telemetry routing with minimal effort.