From 07fb13d5dacbb9e85f2889ac841ad4b20eee86b4 Mon Sep 17 00:00:00 2001 From: Leonardo Mora Castro Date: Thu, 30 Oct 2025 17:22:47 -0600 Subject: [PATCH] [DOC] Make explicit the config path for filtering events from output Fixes #2820 --- docs/sources/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/sources/index.md b/docs/sources/index.md index a38c4e08c1..4c1034eaaf 100644 --- a/docs/sources/index.md +++ b/docs/sources/index.md @@ -128,10 +128,10 @@ application dell_poweredge_cmc[sc4s-network-source] { ### Filtering events from output -In some cases specific events may be considered "noise" and functionality must be implemented to prevent forwarding of these events to Splunk -In version 2.0.0 of SC4S a new feature was implemented to improve the ease of use and efficiency of this progress. +In some cases specific events may be considered "noise" and functionality must be implemented to prevent forwarding of these events to Splunk. +In version 2.0.0 of SC4S a new feature was implemented to improve the ease of use and efficiency of this process. -The following example will "null_queue" or drop cisco IOS device events at the debug level. Note Cisco does not use the PRI to indicate DEBUG a message filter is required. +The following `/opt/sc4s/local/config/app_parsers/cisco_ios_debug-postfilter.conf` example will "null_queue" or drop cisco IOS device events at the debug level. Note Cisco does not use the PRI to indicate DEBUG; a message filter is required. ```c block parser cisco_ios_debug-postfilter() { @@ -239,4 +239,4 @@ sets: vendor = < example vendor > product = < example product > tag = .source.s_EAMPLEVENDOR_EXAMPLEPRODUCT_GROUP01-002 -``` \ No newline at end of file +```