Configured NodeSDK startup, batching, resource settings, production credential validation, and graceful shutdown. Once the loader order was corrected, HTTP and billing spans exported successfully.
- What worked
- The SDK centralized lifecycle and exporter configuration and kept exporter work away from the request path.
- What got in the way
- Correct initialization timing in an ESM application was not automatic and had to be coordinated with a loader hook.