Skip to content
Discussion options

You must be logged in to vote

Vector now has an azure_logs_ingestion sink for the DCR-based API.

Microsoft's Logs Ingestion API setup guide covers the Azure side: create the custom table and DCR, then grant the sending identity the Monitoring Metrics Publisher role on that DCR. The events must match the DCR's input stream schema.

For a local test using an already signed-in Azure CLI:

sinks:
  azure:
    type: azure_logs_ingestion
    inputs: [your_source_or_transform]
    endpoint: https://my-dce-5kyl.eastus-1.ingest.monitor.azure.com
    dcr_immutable_id: dcr-000a00a000a00000a000000aa000a0aa
    stream_name: Custom-MyTable
    auth:
      azure_credential_kind: azure_cli

Use your ingestion endpoint, DCR immutable ID,…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by pront
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
provider:azure Anything `azure` service provider related sink:azure_monitor_logs Anything `azure_monitor_logs` sink related
2 participants