Skip to content

Cleanup per request export readme #150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fpfp100 merged 1 commit into from
Jan 21, 2026
Merged

Cleanup per request export readme #150

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 1 addition & 14 deletions packages/agents-a365-observability/PER_REQUEST_EXPORT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.