From 90696b220468b4e0ee700c8cb5a0ee045bfb818d Mon Sep 17 00:00:00 2001 From: jsl517 Date: Wed, 21 Jan 2026 11:57:11 -0800 Subject: [PATCH] clean up --- .../PER_REQUEST_EXPORT.md | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/packages/agents-a365-observability/PER_REQUEST_EXPORT.md b/packages/agents-a365-observability/PER_REQUEST_EXPORT.md index c00bb7a..3e9124f 100644 --- a/packages/agents-a365-observability/PER_REQUEST_EXPORT.md +++ b/packages/agents-a365-observability/PER_REQUEST_EXPORT.md @@ -57,17 +57,4 @@ Per-request buffering can increase memory usage and cause export bursts during t - `A365_PER_REQUEST_MAX_TRACES` (default `1000`): caps concurrently buffered traces. - `A365_PER_REQUEST_MAX_SPANS_PER_TRACE` (default `5000`): caps buffered ended spans per trace. -Set to `0` (or negative) to disable a specific guardrail. - -## Interaction with batch export - -- **Batch export mode** (`ENABLE_A365_OBSERVABILITY_PER_REQUEST_EXPORT` not enabled) requires `tokenResolver` so the exporter can resolve tokens during export. -- **Per-request export mode** uses the token from OpenTelemetry Context; a `tokenResolver` is not required. - -## Troubleshooting - -If you see: `No token available in OTel Context for per-request export` - -- Ensure `ENABLE_A365_OBSERVABILITY_PER_REQUEST_EXPORT=true`. -- Ensure your request handler is wrapped in `runWithExportToken(...)`. -- Ensure the work that creates spans runs within the same async call chain (avoid detaching work into separate processes/worker threads without propagating context). +Set to `0` (or negative) to disable a specific guardrail. \ No newline at end of file