From 8420e1f9d9768bbff6dfdd78f6784e3d4efbd0e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Casey=20Watson=20=E2=98=81=EF=B8=8F?= <1120131+caseywatson@users.noreply.github.com> Date: Thu, 25 Jul 2024 17:12:37 -0500 Subject: [PATCH] Update _index.md --- docs/content/tools/collector/_index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/content/tools/collector/_index.md b/docs/content/tools/collector/_index.md index 6f7c21439..4ea5d7954 100644 --- a/docs/content/tools/collector/_index.md +++ b/docs/content/tools/collector/_index.md @@ -242,7 +242,9 @@ Given this configuration... - Next, the script will find all KQL files in `.\some_queries` and add them to the run. - If a new query has the same ID (`recommendationId`) as an existing query, the existing query will be overwritten. - If there is no existing query, the new query will be added to the run. -- Next, the script will look for all queries in the `c:\queries\some_more_queries` and apply the same logic as before: if a query has already been loaded with the same ID, it will replace the existing query; otherwise, it will simply load the new query. Note that query paths can be absolute or relative to the location of the running script. +- Next, the script will look for all queries in the `c:\queries\some_more_queries` and apply the same logic as before: if a query has already been loaded with the same ID, it will replace the existing query; otherwise, it will simply load the new query. + +> Note that query paths can be absolute or relative to the location of the running script. # Examples for Well-Architected Reliability Assessment (WARA) v2 Collector Script