From e3f258a9357da8526f224eee916fb66d11897bcc Mon Sep 17 00:00:00 2001 From: Luca Belluccini Date: Thu, 8 Aug 2024 19:50:32 +0200 Subject: [PATCH] [DOCS] Update link --- .../ingest-management/troubleshooting/troubleshooting.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc b/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc index 88abb854a..a81b142c3 100644 --- a/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc +++ b/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc @@ -102,7 +102,7 @@ When you use an {agent} integration in which TSDB (Time Series Database) is enab This can occur if you have a component template defined that includes a `_source` attribute, which conflicts with the `_source: synthetic` setting used when TSDB is enabled. -For details about the error and how to resolve it, refer to the section `Runtime fields cannot be used in TSDB indices` in the Innovation Hub article link:https://support.elastic.dev/knowledge/view/9363b9fd[TSDB enabled integrations for {agent}]. +For details about the error and how to resolve it, refer to the section `Runtime fields cannot be used in TSDB indices` in the Innovation Hub article link:https://support.elastic.co/knowledge/9363b9fd[TSDB enabled integrations for {agent}]. [discrete] [[agents-in-cloud-stuck-at-updating]]