Skip to content

Commit 292812f

Browse files
docs: cross-link to manual instrumentation guide
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 7d28542 commit 292812f

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

‎docs/integrating-with-existing-opentelemetry.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22

33
This guide is for developers whose application **already** initializes OpenTelemetry — for example with `azure-monitor-opentelemetry`, an OTLP collector, or a vendor-specific exporter — and who want Agent 365 spans to flow alongside their existing telemetry. If you're starting fresh, see the [observability-core README](../libraries/microsoft-agents-a365-observability-core/README.md) for the standalone setup.
44

5+
> **Don't want the SDK dependency at all?** See [Manual Agent 365 span instrumentation](./manual-a365-span-instrumentation.md) for how to set the right attributes and export to the A365 backend using only `opentelemetry-sdk` + `requests`.
6+
57
## The integration rule
68

79
> **Initialize your existing OpenTelemetry stack first, then call Agent 365's `configure()`.** The SDK detects the existing `TracerProvider` and adds its processors to it. Your existing backend receives every span; the Agent 365 backend also receives spans when `ENABLE_A365_OBSERVABILITY_EXPORTER=true` and a `token_resolver` is provided (otherwise `configure()` falls back to `ConsoleSpanExporter`).

0 commit comments

Comments
 (0)