Skip to main content

Event Driven (Instant)

Azure Event Grid can notify Chipper when a blob is created. Keep the container SAS token configured as well: the notification announces the blob, while the token authorizes Chipper to read it.

Prepare the source​

  1. Open Configure → Log Sources → New log source and choose the instrument.
  2. Choose Existing cloud storage → Azure and enter the storage account, container, SAS token, and the instrument's log prefix.
  3. Complete the connection check and select Instant import.
  4. Copy the Event Grid webhook URL shown by the wizard. If the environment has no webhook, contact support or use scheduled import.

Enable Event Grid​

If needed, register Event Grid in the subscription that owns the storage account:

SUBSCRIPTION_ID="<your-subscription-id>"
az login
az account set --subscription "$SUBSCRIPTION_ID"
az provider register --namespace Microsoft.EventGrid
az provider show --namespace Microsoft.EventGrid --query registrationState

Create the subscription​

In the Azure portal, open the storage account's Events page and create an event subscription:

  • Event schema: Event Grid Schema.
  • Event type: Microsoft.Storage.BlobCreated.
  • Endpoint type: Web Hook.
  • Endpoint: the exact URL supplied by Chipper.
  • Subject begins with: /blobServices/default/containers/<container>/blobs/<prefix>. Include /blobs/; use an empty prefix to cover the selected container.

The subject layout is defined by the Azure Blob Storage event schema. Review any configured subscription expiration against the intended monitoring period, then create the subscription. Azure sends a validation event to the webhook.

Chipper cannot inspect Event Grid subscriptions with a container SAS token. Confirm the setup manually in the wizard, finish creating the source, then add a representative blob under the configured prefix. Check Investigate → Log Files for the resulting file and processing status. For failures, include the source name and approximate upload time when contacting support.