Microsoft Sentinel
Developer and API

Monitor Data Connector Health

In brief

The documentation now explains how to use the Defender portal’s Data & connectors Overview tab to review connector counts, ingestion volume and growth, errors, table fluctuations, and ingestion latency, with links to connector and table details.

What Defender admins need to know

Administrators can use one workspace-level view to identify connector failures and investigate table-level ingestion issues. No action is required.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

The following features allow you to perform this monitoring from within Microsoft Sentinel:

  • Data & connectors Overview tab (preview): In the Microsoft Defender portal, review connector counts, ingestion volume and growth, connector errors, table ingestion fluctuations, and ingestion latency in one workspace-level view.
  • Data collection health monitoring workbook: This workbook provides additional monitors, detects anomalies, and gives insight regarding the workspace’s data ingestion status. You can use the workbook’s logic to monitor the general health of the ingested data, and to build custom views and rule-based alerts.
  • SentinelHealth data table: Querying this table provides insights on health drifts, such as latest failure events per connector, or connectors with changes from success to failure states, which you can use to create alerts and other automated actions. The SentinelHealth data table is currently supported only for selected data connectors, such as Amazon Web Services, Dynamics 365, Office 365, and others listed in the Supported data connectors section later in this article.
  • View the health and status of your connected SAP systems: Review health information for your SAP systems under the SAP data connector, and use an alert rule template to get information about the health of the SAP agent's data collection.

This article explains how to use the Data & connectors Overview tab in the Defender portal, the data collection health monitoring workbook and the SentinelHealth data table to monitor data connector health, run diagnostic queries, and configure automated alerts for health drifts.

Monitor connector health and ingestion in the Defender portal (preview)

Use the Overview tab on the Data & connectors page to review ingestion trends and identify connectors and tables that need attention. This experience is available in public preview in commercial cloud environments. Microsoft Sentinel must be onboarded to the Microsoft Defender portal, with unified role-based access control enabled. To view connector errors, enable Microsoft Sentinel health monitoring for the workspace and ensure that connector health events are being collected in the SentinelHealth table.

  1. In the Microsoft Defender portal, select Setup & configuration > Data & connectors.

  2. Select the Overview tab.

  3. Select a time range and review the following information:

    InformationWhat to review
    Connector countsTotal installed connectors, connected connectors, and connectors with errors.
    Total ingestion volumeCombined ingestion volume across the Analytics and Data Lake tiers for the selected time range.
    Month-over-month volume growthPercentage change in combined Analytics and Data Lake ingestion volume over the last 30 days compared with the preceding 30 days. This comparison is independent of the selected time range.
    Ingestion volume and growth by tierIngestion volumes for the Analytics and Data Lake tiers, and their growth percentages for the selected time range.
    Ingestion volume trendDaily ingestion volume with an average reference to help you compare daily volumes.
    Connectors that need attentionConnector errors reported in the SentinelHealth table, including error type, failure count, and last successful ingestion.
    Table ingestion fluctuationsTables with unexpected ingestion-volume spikes or drops, with comfigurable thresholds.
    Data ingestion volume by tablePer-day volume trends of top ingesting tables, ranked by daily volume.
    Ingestion latency by tablePer-day trend of latency or time between data generation and availability for use.
  4. Review Connectors that need attention to identify reported connector failures. Use the Connectors tab to find the affected connector and review its configuration and health.

  5. Review table ingestion fluctuations, volume, and latency to identify tables that need further investigation. Use the Tables tab to review table details.

    Screenshot that shows monitor connector health, ingestion volumes, and trends in one view.

    Screenshot that shows investigate table-level ingestion volumes and latency to identify potential issues.

Use the health monitoring workbook