From 68080e5d2461eb9f5d06cd45bad212af173302a1 Mon Sep 17 00:00:00 2001 From: AlteredCoder <64792091+AlteredCoder@users.noreply.github.com> Date: Mon, 31 May 2021 14:48:26 +0200 Subject: [PATCH] update documentation for cscli metrics (#814) Co-authored-by: AlteredCoder --- docs/v1.X/docs/observability/command_line.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/v1.X/docs/observability/command_line.md b/docs/v1.X/docs/observability/command_line.md index 3a71cb792..856d94ef9 100644 --- a/docs/v1.X/docs/observability/command_line.md +++ b/docs/v1.X/docs/observability/command_line.md @@ -19,6 +19,10 @@ The metrics are split in 3 main sections : For example, if you have a source that has mostly unparsed logs, you know you might be missing some parsers. As well, if you have scenarios that are never instantiated, it might be a hint that they are not relevant to your configuration. + Furthermore, you might see parsers called `child-` while calling `cscli metrics`. This correspond to all nodes belonging to a parser. Their metrics + (HITS, PARSED, UNPARSED) are gather by default. If you want to identify metrics for a specific parser node, you just have to set a name for this node in your parser configuration. + +
{{v1X.cli.name}} metrics example ```bash