An Azure data analytics service for real-time analysis on large volumes of data streaming from sources including applications, websites, and internet of things devices.
There are known scenarios where Azure Data Explorer analytics (Insights, dashboards, or Data Explorer-based views) show no data or appear unavailable, but they are typically configuration or health issues rather than a global outage.
Check the following common causes:
- Verify diagnostic logs are enabled
- If Usage, Tables, Cache, or similar analytics views are empty, diagnostic logs might not be enabled for the cluster.
- For each Azure Data Explorer cluster that should appear in analytics/Insights, enable diagnostic logs and send them to a Log Analytics workspace.
- Ensure at least these categories are enabled: Command, Query, TableDetails, and TableUsageStatistics.
- Data isn’t retroactive: analytics will only start populating after logs are enabled and activity occurs on the cluster.
- Allow time for data to appear
- Even after enabling logs, data can take from hours up to a day to appear, depending on cluster activity volume.
- Check subscription and resource selection
- In workbooks/Insights or Grafana dashboards, ensure the correct subscription, resource group, cluster, and workspace are selected.
- If a selected subscription or resource group doesn’t contain any Azure Data Explorer clusters, analytics views will be empty.
- Confirm cluster health
- In the Azure portal, open the cluster’s Resource health:
- Available: cluster is healthy.
- Degraded: ingestion or performance issues may affect analytics completeness.
- Unavailable: queries/ingestion (and thus analytics) may fail; if this persists, contact support.
- Unknown: Resource Health hasn’t received data for >10 minutes or the cluster is stopped; analytics may not update until the state changes.
- If using Azure Managed Grafana
- Open the Azure Managed Grafana endpoint and a pre-provisioned dashboard such as Azure Data Explorer Cluster Resource Insights.
- Ensure dropdowns at the top (data source, subscription, resource group, namespace, resource, workspace) are correctly populated with a resource group that actually contains an Azure Data Explorer cluster.
- Verify the Azure Data Explorer data source configuration: Azure cloud, Cluster URL, Directory (tenant) ID, Application (client) ID, and Client secret must be correct, and Microsoft Entra ID authentication must be properly set up.
- Ensure the Azure Data Explorer instance firewall does not block access from Azure Managed Grafana; the database must be reachable from the public internet.
If, after these checks, analytics are still unavailable, review Resource Health for ongoing platform issues and then open a support request if the cluster remains degraded or unavailable.
References: