Skip to content

Commit f6c406e

Browse files
authored
Update near-real-time-rules.md
1 parent 9cef79b commit f6c406e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/sentinel/near-real-time-rules.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,7 @@ The following limitations currently govern the use of NRT rules:
3737

3838
(Since the NRT rule type is supposed to approximate **real-time** data ingestion, it doesn't afford you any advantage to use NRT rules on log sources with significant ingestion delay, even if it's far less than 12 hours.)
3939

40-
1. As this type of rule is new, its syntax is currently limited but will gradually evolve. Therefore, at this time the following restrictions are in effect:
41-
42-
1. The query defined in an NRT rule can reference **only one table**. Queries can, however, refer to multiple watchlists.
40+
1. The syntax for this type of rule is gradually evolving. At this time the following limitations remain in effect:
4341

4442
1. Because this rule type is in near real time, we have reduced the built-in delay to a minimum (two minutes).
4543

@@ -49,6 +47,8 @@ The following limitations currently govern the use of NRT rules:
4947

5048
1. Event grouping is now configurable to a limited degree. NRT rules can produce up to 30 single-event alerts. A rule with a query that results in more than 30 events will produce alerts for the first 29, then a 30th alert that summarizes all the applicable events.
5149

50+
1. Queries defined in an NRT rule can now reference **more than one table**.
51+
5252
## Next steps
5353

5454
In this document, you learned how near-real-time (NRT) analytics rules work in Microsoft Sentinel.

0 commit comments

Comments
 (0)