Skip to content

Commit 2ef2b61

Browse files
committed
Advanced scheduling of analytics rules
1 parent 0fa246d commit 2ef2b61

File tree

4 files changed

+28
-3
lines changed

4 files changed

+28
-3
lines changed

articles/sentinel/detect-threats-custom.md

Lines changed: 20 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Analytics rules search for specific events or sets of events across your environ
3030

3131
:::image type="content" source="media/tutorial-detect-threats-custom/create-scheduled-query-small.png" alt-text="Create scheduled query" lightbox="media/tutorial-detect-threats-custom/create-scheduled-query-full.png":::
3232

33-
### Analytics rule wizard - General tab
33+
### Analytics rule wizard—General tab
3434

3535
- Provide a unique **Name** and a **Description**.
3636

@@ -109,15 +109,32 @@ In the **Set rule logic** tab, you can either write a query directly in the **Ru
109109
110110
:::image type="content" source="media/tutorial-detect-threats-custom/set-rule-logic-tab-2.png" alt-text="Set query schedule and event grouping" lightbox="media/tutorial-detect-threats-custom/set-rule-logic-tab-all-2-new.png":::
111111
112-
- Set **Run query every** to control how often the query is run - as frequently as every 5 minutes or as infrequently as once every 14 days.
112+
- Set **Run query every** to control how often the query is run—as frequently as every 5 minutes or as infrequently as once every 14 days.
113113
114-
- Set **Lookup data from the last** to determine the time period of the data covered by the query - for example, it can query the past 10 minutes of data, or the past 6 hours of data. The maximum is 14 days.
114+
- Set **Lookup data from the last** to determine the time period of the data covered by the query—for example, it can query the past 10 minutes of data, or the past 6 hours of data. The maximum is 14 days.
115+
116+
- For the new **Start running** setting (in Preview):
117+
118+
- Leave it set to **Automatically** to continue the original behavior: the rule will run for the first time immediately upon being created, and after that at the interval set in the **Run query every** setting.
119+
120+
- Toggle the switch to **At specific time** if you want to determine when the rule first runs, instead of having it run immediately. Then choose the date using the calendar picker and enter the time in the format of the example shown.
121+
122+
:::image type="content" source="media/tutorial-detect-threats-custom/advanced-scheduling.png" alt-text="Screenshot of advanced scheduling toggle and settings.":::
123+
124+
Future runnings of the rule will occur at the specified interval after the first running (see **Advanced scheduling** note below).
125+
126+
The line of text under the **Start running** setting (with the information icon at its left) summarizes the current query scheduling and lookback settings.
115127
116128
> [!NOTE]
129+
>
117130
> **Query intervals and lookback period**
118131
>
119132
> These two settings are independent of each other, up to a point. You can run a query at a short interval covering a time period longer than the interval (in effect having overlapping queries), but you cannot run a query at an interval that exceeds the coverage period, otherwise you will have gaps in the overall query coverage.
120133
>
134+
> **Advanced scheduling**
135+
>
136+
> If you choose to start the running of a rule at a specific time (instead of automatically upon creation), be aware that the **actual** first run time of the rule may vary from the time you specified by up to half an hour in either direction. In any case, the interval for future runnings will be measured from the actual starting time of the previous run, not from the specified time.
137+
>
121138
> **Ingestion delay**
122139
>
123140
> To account for **latency** that may occur between an event's generation at the source and its ingestion into Microsoft Sentinel, and to ensure complete coverage without data duplication, Microsoft Sentinel runs scheduled analytics rules on a **five-minute delay** from their scheduled time.
9.41 KB
Loading
6.84 KB
Loading

articles/sentinel/whats-new.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,14 @@ See these [important announcements](#announcements) about recent changes to feat
1818

1919
[!INCLUDE [reference-to-feature-availability](includes/reference-to-feature-availability.md)]
2020

21+
## February 2023
22+
23+
### Advanced scheduling for analytics rules (Preview)
24+
25+
To give you more flexibility in scheduling your analytics rule execution times, and avoid potential conflicts, Microsoft Sentinel now allows you to determine when newly created analytics rules will run for the first time. The default behavior is as it has been: for them to run immediately upon creation.
26+
27+
[Learn more about advanced scheduling](detect-threats-custom.md#query-scheduling-and-alert-threshold).
28+
2129
## January 2023
2230

2331
- [Monitor SAP system health (Preview)](#monitor-sap-system-health-and-role-preview)

0 commit comments

Comments
 (0)