Skip to main content

Azure Synapse Analytics

Thumbnail icon

Azure Synapse Analytics is an enterprise analytics service that accelerates time to insight across data warehouses and big data systems. It gives you the freedom to query data on your terms, using either serverless or dedicated resources—at scale. This integration helps in monitoring integrations in your Synapse workspaces, tracking resource utilization (memory, CPU, connections etc) and query load across Spark pools and dedicated SQL pools.

Log types

For Azure Synapse Analytics, you can collect the following logs:

Setup

Azure service sends monitoring data to Azure Monitor, which can then stream data to Eventhub. Sumo Logic supports:

You must explicitly enable diagnostic settings for each Synapse workspace, dedicated SQL pool, or Apache Spark pool you want to monitor. You can forward logs to the same event hub provided they satisfy the limitations and permissions as described here.

When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: Azure/SynapseAnalytics/Logs, Azure/SynapseAnalytics/Metrics.

Configure logs collection

In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.

  1. To set up the Azure Event Hubs cloud-to-cloud source in Sumo Logic portal, refer to our Azure Event Hubs source documentation.
  2. To create the Diagnostic settings in Azure portal, refer to the Azure documentation.
    • Choose Stream to an event hub as the destination.
    • Select allLogs.
    • Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy RootManageSharedAccessKey as the policy name.

You must explicitly enable diagnostic settings for Synapse workspace, dedicated SQL pool, or Apache Spark pool you want to monitor.

Troubleshooting

Azure Event Hubs Source

Common error types are described here.

You can try restarting the source for ThirdPartyConfig errors.

Legal
Privacy Statement
Terms of Use

Copyright © 2023 by Sumo Logic, Inc.