Skip to main content
Question

Native Dashboards: alert-level closure reason / root cause is not queryable

  • July 28, 2026
  • 3 replies
  • 49 views

JensW
Forum|alt.badge.img+4

In Google SecOps SOAR, the closure verdict (reason, root cause, comment, closing time) is stored per alert. A case can contain many alerts closed with different root causes at different times. In the Native Dashboards data model, however, closure information appears to be exposed only at case level (case.closure_details.*). We cannot find any field path that returns the per-alert closure verdict.

As a result, alert-level closure reporting (e.g. "alert true-positive rate", "root cause distribution per alert") cannot be built in Native Dashboards, and naive queries silently produce wrong numbers.

 

What we are trying to build:

A dashboard panel that answers: "For closed alerts, how many were closed with which closure reason / root cause, over time?" at alert granularity, not case granularity.

 

Is the per-alert closure verdict (reason, root cause, comment, closing time as stored in alertCards[].closureDetails) exposed in any Native Dashboards data source? If yes, what is the exact field path?

The case.closure_details.* returns a single value per case,. Which alert's closure does this value come from? The most recently closed alert?

3 replies

Likshit
Forum|alt.badge.img+1
  • New Member
  • July 28, 2026

Even I need a solution for this.


a_aleinikov
Forum|alt.badge.img+8
  • Bronze 2
  • July 28, 2026

Based on the current Native Dashboards schema, I do not see alert-level closure details exposed under case.alerts. The documented case.closure_details.* fields represent the closure of the case itself, so they should not be used to calculate closure reasons or root causes per alert.

Although SOAR supports closing individual alerts with their own Reason and Root Cause, those values do not appear to be available in the Native Dashboards data model. Therefore, alert-level true-positive rates or root-cause distributions cannot currently be calculated reliably there.

I would recommend opening a support case or feature request to expose alertCards[].closureDetails as part of the alert object. I would also avoid assuming that case.closure_details belongs to the most recently closed alert—it appears to describe only the case closure.


Forum|alt.badge.img+2

I believe case closure reason/root cause is available only for case closure (considering similar type of alerts are grouped to a particular case)