Skip to content

[9.1 & Serverless][ResponseOps] ES|QL rule type ungrouped alerts #2015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 16 commits into from
Jul 7, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
obs docs
  • Loading branch information
nastasha-solomon committed Jul 2, 2025
commit 7dad94d13d6a92adadcd9ce37db9c4437e89afce
Original file line number Diff line number Diff line change
Expand Up @@ -71,10 +71,18 @@ When you create an {{es}} query rule, your choice of query type affects the info
Threshold
: Defines a threshold value and a comparison operator (`is above`, `is above or equals`, `is below`, `is below or equals`, or `is between`). The value calculated by the aggregation is compared to this threshold.

3. Set the time window, which defines how far back to search for documents.
4. If you use query DSL, KQL, or Lucene, set the number of documents to send to the configured actions when the threshold condition is met.
5. If you use query DSL, KQL, or Lucene, choose whether to avoid alert duplication by excluding matches from the previous run. This option is not available when you use a grouping field.
6. Set the check interval, which defines how often to evaluate the rule conditions. Generally this value should be set to a value that is smaller than the time window, to avoid gaps in detection.
3. If you use {{esql}}, specify a time field and how to group alerts.

Time field
: Specify the time field to use when filtering query results by the time window that you specify. You can choose `@timestamp`, `timestamp`, or `utc_time`.

Alert group
: Select **Create an alert if matches are found** to create a single alert when the query matches multiple events. Select **Create an alert for each row** to create an alert for each query match. Whenever possible, each alert will have a unique ID.

4. Set the time window, which defines how far back to search for documents.
5. If you use query DSL, KQL, or Lucene, set the number of documents to send to the configured actions when the threshold condition is met.
6. If you use query DSL, KQL, or Lucene, choose whether to avoid alert duplication by excluding matches from the previous run. This option is not available when you use a grouping field.
7. Set the check interval, which defines how often to evaluate the rule conditions. Generally this value should be set to a value that is smaller than the time window, to avoid gaps in detection.


## Test your query [observability-create-elasticsearch-query-rule-test-your-query]
Expand Down
Loading