From 62e8e516548c39200b1c79acd73b5b3b999f9284 Mon Sep 17 00:00:00 2001 From: Brandon Morelli Date: Wed, 17 Apr 2024 19:39:04 -0700 Subject: [PATCH] Update logs-threshold-alert.asciidoc (#3799) --- docs/en/observability/logs-threshold-alert.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/observability/logs-threshold-alert.asciidoc b/docs/en/observability/logs-threshold-alert.asciidoc index 8e2a706320..8a68bdb939 100644 --- a/docs/en/observability/logs-threshold-alert.asciidoc +++ b/docs/en/observability/logs-threshold-alert.asciidoc @@ -21,7 +21,7 @@ The comparators available for conditions depend on the chosen field. The combina * Aggregatable fields: *is* or *is not*. * Non-aggregatable fields: *matches*, *does not match*, *matches phrase*, *does not match phrase*. ** *Matches* queries some or all of the contents of your entered value regardless of order. For example, `WITH message MATCHES your example message` looks for messages containing the words `your` and `example` and `message` and returns results with some or all of those words. -** *Matches phrase* queries the exact contents of your entered value. For example, `WITH message MATCHES your example message` looks for the phrase `your example message` and returns results with that exact phrase. +** *Matches phrase* queries the exact contents of your entered value. For example, `WITH message MATCHES PHRASE your example message` looks for the phrase `your example message` and returns results with that exact phrase. There are several key supported use cases. You can create rules based on fields containing or matching a text pattern, rules based on a numeric field and arithmetic operator, or a single rule with multiple conditions.