maple-onboarding-style

Standardize OpenTelemetry instrumentation by enforcing native OTel APIs and the @maple/otel-helpers withSpan helper for bounded business spans, ensuring consistent observability data and eliminating trace correlation gaps across Maple microservices.

Configure VCS resource attributes for OpenTelemetry traces by applying standardized semantic convention attribute formatting, which binds version control metadata to your telemetry data for better trace correlation and debugging context.

Implement LLM telemetry by applying standardized LLM metrics collection patterns alongside native OpenTelemetry APIs, ensuring your LLM-powered applications emit compatible observability data and capture accurate performance metrics.

You should avoid custom telemetry wrappers; this standardization enforces official OpenTelemetry APIs and the @maple/otel-helpers withSpan helper to prevent inconsistent observability data and ensure proper trace correlation.

Validate OpenTelemetry bootstrap loads by running durable smoke checks that exercise instrumented spans, logs, and metrics, catching setup errors early before they cause missing telemetry data in production.

Inconsistent observability data usually stems from non-standard span naming and missing telemetry coverage; standardizing OTel semantic conventions and resource attribute formatting eliminates these gaps and improves trace correlation.