@@ -634,6 +634,23 @@ GET /_eql/search/FmNJRUZ1YWZCU3dHY1BIOUhaenVSRkEaaXFlZ3h4c1RTWFNocDdnY2FSaERnUTo
634634// TEST[skip: no access to search ID]
635635====
636636
637+ You can use the <<delete-async-eql-search-api,delete async EQL search API>> to
638+ manually delete an async EQL search before the `keep_alive` period ends. If the
639+ search is still ongoing, this cancels the search request.
640+
641+ .*Example*
642+ [%collapsible]
643+ ====
644+ The following delete async EQL search API request deletes an async EQL search
645+ and its results.
646+
647+ [source,console]
648+ ----
649+ DELETE /_eql/search/FmNJRUZ1YWZCU3dHY1BIOUhaenVSRkEaaXFlZ3h4c1RTWFNocDdnY2FSaERnUTozNDE=?keep_alive=5d
650+ ----
651+ // TEST[skip: no access to search ID]
652+ ====
653+
637654[discrete]
638655[[eql-search-store-sync-eql-search]]
639656=== Store synchronous EQL searches
@@ -642,8 +659,7 @@ By default, the EQL search API only stores async searches that cannot be
642659completed within the period set by the `wait_for_completion_timeout` parameter.
643660
644661To save the results of searches that complete during this period, set the
645- `keep_on_completion` parameter to `true`. Note these saved searches are still
646- subject to the storage retention period set by the `keep_alive` parameter.
662+ `keep_on_completion` parameter to `true`.
647663
648664[%collapsible]
649665.*Example*
@@ -694,6 +710,13 @@ GET /_eql/search/FjlmbndxNmJjU0RPdExBTGg0elNOOEEaQk9xSjJBQzBRMldZa1VVQ2pPa01YUTo
694710// TEST[skip: no access to search ID]
695711====
696712
713+ Saved synchronous searches are still subject to the storage retention period set
714+ by the `keep_alive` parameter. After this period, the search and its saved
715+ results are deleted.
716+
717+ You can also manually delete saved synchronous searches using the
718+ <<delete-async-eql-search-api,delete async EQL search API>>.
719+
697720[discrete]
698721[[eql-search-case-sensitive]]
699722=== Run a case-sensitive EQL search
0 commit comments