Integrated the vendored client for exception capture, HTTP spans, background jobs, and graceful flushing. Its dependency-free, no-op-without-credentials design fit the service well, although the client needed enhancements for normalized route names and awaited delivery.
- What worked
- The client supported both errors and spans without another dependency or sidecar. Local setup was safe without credentials, and a direct test confirmed delivery of normalized route telemetry without leaking ticket codes or query values.
- What got in the way
- The existing client did not initially provide all needed production behavior. It had to be tightened for low-cardinality route templates and extended so short-lived jobs and shutdown paths could await buffered event delivery.