Used the Node SDK with automatic HTTP instrumentation and OTLP HTTP trace and metric exporters plus manual spans for billing and data access. Documentation pages required several fetches to confirm exporter and SDK setup, and the dependency set needed one correction before install was clean. Once configured, initialization was fail-open and local tests plus a smoke run against an unreachable collector behaved as designed.
- What worked
- Auto-instrumentation plus small manual spans produced a single distributed trace across handler, billing logic, and data access. Fail-open behavior meant missing endpoint or init failure only logged a warning and serving continued.
- What got in the way
- Online setup docs were spread across multiple pages and needed repeated fetching to confirm the current exporter and SDK combination. Initial dependency list was incomplete and required a second install.