What problem does it solve?
Inconsistent OpenTelemetry attribute keys, span status codes, and resource attributes across Maple's TypeScript, Rust, and future Python services break Tinybird materialized view pre-extractions, dashboard filters, and service map rendering, leading to missing observability data and incorrect analytics.
Core Features & Use Cases
- Cross-language attribute conventions: Canonical spellings for custom span attributes including the
maple.* vendor namespace, query.*, cache.*, tenant.*, and db.* groups, with parallel implementation snippets for TypeScript (Effect), Rust (tracing), and Python.
- Load-bearing observability rules: Title Case span status codes, dual-emit deployment environment resource attributes, Tinybird MV pre-extracted column alignment, and mandatory loop-prevention guard requirements that are critical for dashboard accuracy and trace volume stability.
- Use cases: Adding instrumentation to new code paths, reviewing PRs that touch observability-related files, configuring OTLP exporters and tracer providers, and adding new Tinybird MV columns without breaking existing dashboards.
Quick Start
Use this skill to validate that your new WarehouseQueryService span emits all required canonical attributes and uses the correct Title Case status code before merging your instrumentation PR.