Summary
The distro Agent365Exporter supports useS2SEndpoint, but the high-level useMicrosoftOpenTelemetry({ a365: { ... } }) API doesn't expose it. For OBO scenarios, you need to use Agent365Exporter directly instead of the high-level API.
// High-level API — no useS2SEndpoint option available
useMicrosoftOpenTelemetry({
a365: {
enabled: true,
tokenResolver: ...,
// useS2SEndpoint not available here
},
});
// Agent365Exporter — useS2SEndpoint is supported
const exporter = new Agent365Exporter({
tokenResolver: ...,
useS2SEndpoint: false, // ✓ works here
clusterCategory: 'prod',
});Request
Expose useS2SEndpoint in the useMicrosoftOpenTelemetry({ a365: { ... } }) config for consistency with the Python and .NET distros:
- Python:
use_microsoft_opentelemetry(a365_use_s2s_endpoint=True/False)
- .NET:
o.Agent365.Exporter.UseS2SEndpoint = true/false
Package
@microsoft/opentelemetry v0.1.0-beta.1
Summary
The distro
Agent365ExportersupportsuseS2SEndpoint, but the high-leveluseMicrosoftOpenTelemetry({ a365: { ... } })API doesn't expose it. For OBO scenarios, you need to useAgent365Exporterdirectly instead of the high-level API.Request
Expose
useS2SEndpointin theuseMicrosoftOpenTelemetry({ a365: { ... } })config for consistency with the Python and .NET distros:use_microsoft_opentelemetry(a365_use_s2s_endpoint=True/False)o.Agent365.Exporter.UseS2SEndpoint = true/falsePackage
@microsoft/opentelemetryv0.1.0-beta.1