@cognipeer/agent-sdk 0.16.0 → 0.18.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/dist/index.cjs +2160 -379
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +596 -38
- package/dist/index.d.ts +596 -38
- package/dist/index.mjs +2154 -380
- package/dist/index.mjs.map +1 -1
- package/dist/{model-rules-Bg9nSqyN.d.cts → model-rules--welxWDw.d.cts} +2 -0
- package/dist/{model-rules-Bg9nSqyN.d.ts → model-rules--welxWDw.d.ts} +2 -0
- package/dist/model-rules.d.cts +1 -1
- package/dist/model-rules.d.ts +1 -1
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -440,7 +440,7 @@ Enable tracing by passing `tracing: { enabled: true }`. Each invocation writes `
|
|
|
440
440
|
|
|
441
441
|
You can disable payload capture with `logData: false` to keep only metrics, or configure sinks such as `httpSink(url, headers?)`, `cognipeerSink(apiKey, url?)`, `otlpSink(endpoint, headers?)`, or `customSink({ onEvent, onSession })` to forward traces after each run. Sensitive headers/callbacks remain in-memory and are never written alongside the trace.
|
|
442
442
|
|
|
443
|
-
Each session/event also carries OTel-compatible correlation identifiers (`traceId`, `rootSpanId`, `spanId`, `parentSpanId`)
|
|
443
|
+
Each session/event also carries OTel-compatible correlation identifiers (`traceId`, `rootSpanId`, `spanId`, `parentSpanId`). `otlpSink` and the `otelTracing` plugin export them as OpenTelemetry GenAI spans (`invoke_agent`, `chat`, `execute_tool`) over OTLP/HTTP JSON or protobuf, with the standard `OTEL_*` variables, optional prompt/response capture and W3C `traceparent` propagation. See the [OpenTelemetry guide](docs/guide/opentelemetry.md).
|
|
444
444
|
|
|
445
445
|
Pass `tracing: { metadata: { ... } }` to attach arbitrary key-value tags (e.g. `{ complexity: "complex" }`) to every payload sent to the sink. The SDK does not interpret these tags itself — they're forwarded as-is so a downstream consumer (e.g. Console) can use them as reporting/attribution dimensions.
|
|
446
446
|
|