A cloud-native SIEM solution that provides intelligent security analytics and threat detection across systems
Hello Justyna Kotowska,
If you’re seeing no results for the SentinelHealth table in Microsoft Sentinel (Germany region), even though you expect Sentinel rules/health monitoring to be active, the most likely explanations are usually around health feature enablement, workspace/connector health coverage, or data not arriving into the Log Analytics workspace.
1) First check: is Sentinel health monitoring enabled for the workspace?
SentinelHealth is the table used for health logs for operations performed by Microsoft Sentinel resources (for example, data connectors and analytics rules). According to the SentinelHealth troubleshooting guidance, you must turn on the Microsoft Sentinel health feature for your workspace before you should expect health records to appear.
What to do
- In Microsoft Sentinel, enable the health monitoring feature (if it’s not already enabled) for that workspace.
- Then allow some time for health events to be generated.
2) Validate that SentinelHealth data is actually being ingested into Log Analytics
Microsoft Sentinel can only query/visualize data that’s present in the Log Analytics workspace. If logs aren’t reaching the workspace, you’ll see empty results.
What to do
- Open Microsoft Sentinel > General > Logs and run a basic query like:
-
SentinelHealth | take 10 - If you still get nothing, that indicates either the health feature isn’t enabled, or ingestion is failing for health events.
-
3) Know what SentinelHealth represents (it’s not “query results” from analytics rules)
One common misunderstanding: SentinelHealth tracks Sentinel resource health/operations, not necessarily the “expected business data” you might be thinking of. So “rules are executing” does not always guarantee you’ll see SentinelHealth rows unless the health monitoring is enabled and producing events, and depending on what operations are being monitored.
(There’s also guidance noting that health monitoring can be connector/rule operation focused, and for verifying actual ingestion into a given log table, you should query that target table directly.)
4) If this is specific to analytics rule integrity
SentinelHealth is used alongside SentinelAudit for analytics rule integrity monitoring. If analytics rule integrity monitoring is relevant for your scenario, check whether that monitoring path is enabled/configured and whether there are recent rule runs that would generate health events.
Follow-up questions (to pinpoint the root cause)
- In the Sentinel workspace, has the Microsoft Sentinel health monitoring feature been enabled for that workspace?
- When you run in Microsoft Sentinel > General > Logs:
SentinelHealth | take 10— do you get zero rows even without filtering by time? - Roughly when were analytics/data connector rules last modified or executed (and are you expecting health events tied to those operations)?
- Is your primary goal to confirm:
- (a) that Sentinel resources are healthy / running, or
- (b) that a specific data table is ingesting logs?
- Are there any recent errors in the health/audit area (for example in
SentinelAudit), or is everything empty?
- (a) that Sentinel resources are healthy / running, or
If you share what you’ve already tried (especially whether health monitoring is enabled), I can narrow it down quickly.