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.