The private Node.js SDK matched the service's Express, database, tracing, metrics, and error-reporting needs. Its startup and reporting APIs were clear enough to integrate, but the package could not be downloaded or exercised because the internal registry was unreachable.
- What worked
- The documented single-agent approach supported early process instrumentation, explicit handled-error reporting, and named spans across both the API and background worker.
- What got in the way
- The private package registry could not be resolved, so installation, live SDK behavior, export delivery, and dependency locking could not be verified.