Skip to content

docs(azure_sentinel): explain where to find the DCE and DCR logs ingestion endpoints - #3202

Open
yassin-berriai wants to merge 2 commits into
mainfrom
litellm_docs_azure_sentinel_dce_endpoint
Open

yassin-berriai wants to merge 2 commits into
mainfrom
litellm_docs_azure_sentinel_dce_endpoint

Conversation

@yassin-berriai

@yassin-berriai yassin-berriai commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

TLDR

#3199 already corrected the "NOT the DCE" claim on the Azure Sentinel page. This PR adds what that change left out, which is where to find each endpoint and when a DCE is required. The Logs Ingestion API accepts either endpoint with the same URI, and the azure_sentinel callback builds that URI from whatever endpoint it is given

Linear ticket

Resolves LIT-11043

Files changed

File Change
docs/observability/azure_sentinel.md Add a paragraph after the endpoint note that says where to find the DCR endpoint (Overview page or properties.endpoints.logsIngestion in JSON view) and the DCE endpoint (Monitor -> Data Collection Endpoints -> Overview -> Logs Ingestion), when a DCE is required (private link, or a DCR without its own logs ingestion endpoint) and that all three resources must share a region. The portal walkthrough step that copies the endpoint also points at the DCE selected in Step 3

The code side was checked on litellm main. AzureSentinelLogger._build_api_endpoint in litellm/integrations/azure_sentinel/azure_sentinel.py returns f"{endpoint.rstrip('/')}/dataCollectionRules/{dcr_immutable_id}/streams/{stream_name}?api-version=2023-01-01" with no check on the endpoint type, and the constructor docstring already says the endpoint is a "Data Collection Endpoint (DCE) or DCR ingestion endpoint"

Screenshots / Proof of Fix

npm run build and python3 scripts/check-docs.py pass locally. Rendered page from the local production build of the merged tip (on top of #3199):

Endpoint note with the new paragraph on where to find each endpoint

Setup guide Step 4 pointing at the DCE as an alternative

Details

Link to Devin session: https://app.devin.ai/sessions/f609b01e9c6a4553ac0570653793a6af
Open in Devin Desktop: https://app.devin.ai/desktop/session/f609b01e9c6a4553ac0570653793a6af?variant=devin
Requested by: @yassin-berriai

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@devin-ai-integration

Copy link
Copy Markdown
Contributor

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

  • Disable automatic comment, CI, and merge conflict monitoring

@vercel

vercel Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
litellm Ready Ready Preview Nov 20, 2026 9:42pm UTC

Request Review

@devin-ai-integration

Copy link
Copy Markdown
Contributor

@litereview code-review

…ntinel_dce_endpoint

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

# Conflicts:
#	docs/observability/azure_sentinel.md
@devin-ai-integration devin-ai-integration Bot changed the title docs(azure_sentinel): accept a DCE or DCR logs ingestion endpoint docs(azure_sentinel): explain where to find the DCE and DCR logs ingestion endpoints Nov 20, 2026

This branch was successfully deployed

1 active deployment
Preview — bd258f22 Deployed Nov 20, 2026 by vercel[bot]
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.

1 participant