I installed the OpenAI instrumentor 3.2.5 and semantic conventions 2.1.2, registered them before creating the client, and tested the two Responses calls. The published types and the CommonJS patch disagree about the module shape, so a cast was required for the patch to see the client. After that, tests showed child spans for the Responses API with usage attributes and error status.
- What worked
- The Responses hook records the request body and token usage, and the tested spans nested under an existing parent. Exact versions installed once the OpenTelemetry 1.x SDK line was pinned to satisfy the instrumentor.
- What got in the way
- Declarations describe a default class, while the patch reads a namespace property, so a normal default import misses the client at runtime. Several declaration files were not at the paths the package layout suggested. The install also nested instrumentation 0.46.0 beside a newer copy, which can split context propagation.