From 0af22446b58ccf376705fc57ad4a13344c1e7659 Mon Sep 17 00:00:00 2001 From: Colleen McGinnis Date: Fri, 28 Mar 2025 12:04:03 -0500 Subject: [PATCH] remove reliance on redirects --- docs/reference/log-correlation-manual.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/log-correlation-manual.md b/docs/reference/log-correlation-manual.md index 77937299b..99dc63737 100644 --- a/docs/reference/log-correlation-manual.md +++ b/docs/reference/log-correlation-manual.md @@ -49,7 +49,7 @@ This would print a log message along the lines of: ERROR [trace.id=cd04f33b9c0c35ae8abe77e799f126b7 transaction.id=cd04f33b9c0c35ae] an error occurred ``` -For log correlation to work, the trace ids must be extracted from the log message and stored in separate fields in the Elasticsearch document. This can be achieved by [parsing the data by using ingest node](beats://reference/filebeat/configuring-ingest-node.md), in particular by using [the grok processor](elasticsearch://reference/ingestion-tools/enrich-processor/grok-processor.md). +For log correlation to work, the trace ids must be extracted from the log message and stored in separate fields in the Elasticsearch document. This can be achieved by [parsing the data by using ingest node](beats://reference/filebeat/configuring-ingest-node.md), in particular by using [the grok processor](elasticsearch://reference/enrich-processor/grok-processor.md). ```json {