Summary
The migration guide's local validation section (section 14) mentions setting ENABLE_A365_OBSERVABILITY_EXPORTER=false to export spans to the console, but doesn't show how to explicitly enable the console exporter with enableConsoleExporters: true.
Issue
The validation section says:
Set ENABLE_A365_OBSERVABILITY_EXPORTER=false to export spans to the console for local validation.
This relies on the auto-enable behavior (console auto-enables when no other exporter is active). But if the user has Azure Monitor or OTLP configured, console won't auto-enable and they'll see nothing locally.
The guide should explicitly show:
useMicrosoftOpenTelemetry({
enableConsoleExporters: true,
a365: {
enabled: true,
tokenResolver: myResolver,
},
});
And explain that enableConsoleExporters: true forces console output regardless of other exporters being active.
References
Summary
The migration guide's local validation section (section 14) mentions setting
ENABLE_A365_OBSERVABILITY_EXPORTER=falseto export spans to the console, but doesn't show how to explicitly enable the console exporter withenableConsoleExporters: true.Issue
The validation section says:
This relies on the auto-enable behavior (console auto-enables when no other exporter is active). But if the user has Azure Monitor or OTLP configured, console won't auto-enable and they'll see nothing locally.
The guide should explicitly show:
And explain that
enableConsoleExporters: trueforces console output regardless of other exporters being active.References
src/types.ts—enableConsoleExportersproperty