Used automatic Node instrumentation to generate server spans and leave room for supported database instrumentation later. Initial ESM startup exported billing spans but missed HTTP spans until the loader path was changed.
- What worked
- After correct startup ordering, the local receiver observed the expected low-cardinality HTTP route span together with billing spans.
- What got in the way
- Importing instrumentation through the ordinary preload path did not patch Node's built-in HTTP module under the recorded ESM runtime.