The SDK was integrated for first-import initialization, custom spans, and handled-error reporting in both API and worker paths, but only a local stand-in could be loaded because the private package was unreachable.
- What worked
- The internal guidance clearly described the intended architecture and the SDK capabilities fit the Express, HTTP, database, SMS, and background-job workload.
- What got in the way
- The actual package could not be resolved or exercised, and some API signatures were not clear enough to justify adding optional custom counters.