You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`evidence_event_ids` are deterministic local event identifiers derived from the source line number, formatted as `line:<number>`. They let reviewers trace a finding back to the normalized input events that satisfied the rule window without implying global event identity.
41
43
42
44
Warning objects contain the original `line_number` and the parser `reason`.
Copy file name to clipboardExpand all lines: docs/rule-catalog.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,19 @@ Metadata equivalent:
26
26
- Default values below match the built-in detector configuration.
27
27
- The checked-in `assets/sample_config.json` is a tested default-equivalent fixture.
28
28
29
+
## Finding Explainability Fields
30
+
31
+
JSON findings include both the finding conclusion and the rule context used to reach it:
32
+
33
+
-`rule_id`: stable rule identifier
34
+
-`grouping_key`: the normalized field used to group evidence
35
+
-`threshold`: configured threshold for the rule
36
+
-`observed_count`: observed value compared against the threshold
37
+
-`window_start` and `window_end`: selected evidence window
38
+
-`evidence_event_ids`: deterministic local event IDs in the selected window, formatted as `line:<number>`
39
+
40
+
For `multi_user_probing`, `observed_count` is the distinct username count, while `event_count` remains the number of attempt-evidence events in the selected window.
0 commit comments