Microsoft Sentinel
Cloud and workloads

Monitor Sap System Health

In brief

The SAP system health article now links to KQL queries for detecting incomplete collection windows and analyzing truncation markers, daily and projected monthly volume, hourly peaks, and high-volume accounts.

What Defender admins need to know

Administrators can use these queries to investigate ingestion completeness and volume patterns when monitoring SAP data collection.

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.

For the full list of tables and the recommended KQL functions to query them, see Log and table reference for the Microsoft Sentinel solution for SAP applications.

Find gaps and analyze ingestion volume

Recent records confirm that data is arriving, but don't establish that earlier collection windows are complete. Use the gap-detection KQL on GitHub to identify completed time windows without events in ABAPAuditLog. Filter the query to the SAP system and client you want to investigate. Empty windows can reflect normal quiet periods, so check SentinelHealth and SAP Cloud Integration message processing logs before treating them as missing data.

For truncation markers, daily volume, projected monthly volume, hourly peaks, and high-volume accounts, use the SAP ingestion analysis KQL on GitHub. These queries analyze ingested audit data and don't require running the backfill script. Volume projections aren't billing estimates, and high volume alone doesn't justify excluding an account. Review detection coverage and audit requirements with your SAP and security teams before configuring exclusions.

Check the SentinelHealth table for health indicators

The SentinelHealth table in Microsoft Sentinel contains health indicators for the SAP data connector, among others. You can query this table to get a summary of the health of your SAP systems.