Skip to content

docs: clarify correlation header configuration - #2795

Open
Aditya Reddy (adityareddy-dev) wants to merge 1 commit into
microsoft:mainfrom
adityareddy-dev:docs/correlation-header-options-2348
Open

Aditya Reddy (adityareddy-dev) wants to merge 1 commit into
microsoft:mainfrom
adityareddy-dev:docs/correlation-header-options-2348

Conversation

@adityareddy-dev

Copy link
Copy Markdown
Contributor

The README and API comments said correlation headers were added to every request. I clarified the host checks, exclusions, tracing mode and app ID requirement.

Related to #2348

Copilot AI balanced review requested due to automatic review settings November 5, 2026 00:10

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

There are no active review issues for this documentation-only clarification of correlation-header configuration.

No open issues 🎉

What changed in this PR

Clarifies correlation-header configuration in the SDK documentation, addressing the confusion described in #2348. This PR changes documentation only, not runtime behavior.

Changes:

  • Explains how host checks and domain/URL filters determine which requests can receive correlation headers.
  • Clarifies which trace headers each distributed tracing mode adds.
  • Documents that Request-Context requires an available appId.
File Description
shared/​AppInsightsCore/​src/​interfaces/​ai/​IConfig.ts Updates API comments for correlation settings and tracing modes.
README.md Aligns configuration descriptions with header eligibility and app ID requirements.

Review effort: Balanced

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants