From f23dd955ca78b106af49c26a3a86af3a69721f27 Mon Sep 17 00:00:00 2001 From: Felix Barnsteiner Date: Wed, 16 Aug 2023 13:16:24 +0200 Subject: [PATCH] Remove duplicate _index in search response (#3148) (cherry picked from commit fc061935e295dd5835e7338907132ceb484b4a90) --- docs/en/observability/logs-stream.asciidoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/en/observability/logs-stream.asciidoc b/docs/en/observability/logs-stream.asciidoc index 0c19274789..74b7ade0fb 100644 --- a/docs/en/observability/logs-stream.asciidoc +++ b/docs/en/observability/logs-stream.asciidoc @@ -365,7 +365,6 @@ You can see the pipeline extracted the `@timestamp` field: ... "hits": [ { - "_index": ".ds-logs-generic-default-2023.08.09-000001", "_index": ".ds-logs-example-default-2023.08.09-000001", "_id": "RsWy3IkB8yCtA5VGOKLf", "_score": 1, @@ -389,4 +388,4 @@ Check the following common issues for possible solutions: - *Timestamp failure* – If your data has inconsistent date formats, you can set `ignore_failure` to `true` for your date processor. This processes logs with correctly formatted dates and ignores those with issues. - *Incorrect timezone* – Set your timezone using the `timezone` option on the {ref}/date-processor.html[date processor]. -- *Incorrect timestamp format* – Your timestamp can be a Java time pattern or one of the following formats: ISO8601, UNIX, UNIX_MS, or TAI64N. See the {ref}/mapping-date-format.html[mapping date format] for more information on timestamp formats. \ No newline at end of file +- *Incorrect timestamp format* – Your timestamp can be a Java time pattern or one of the following formats: ISO8601, UNIX, UNIX_MS, or TAI64N. See the {ref}/mapping-date-format.html[mapping date format] for more information on timestamp formats.