From f72ebcf179c928f07475b1b059d99bf317f3663c Mon Sep 17 00:00:00 2001 From: "Eric D. Schabell" Date: Tue, 2 Dec 2025 17:04:42 +0100 Subject: [PATCH] Fixes to standardize the kernel logs input plugin doc. Fixes #2270. Signed-off-by: Eric D. Schabell --- pipeline/inputs/kernel-logs.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/pipeline/inputs/kernel-logs.md b/pipeline/inputs/kernel-logs.md index accc1317d..3efe211bd 100644 --- a/pipeline/inputs/kernel-logs.md +++ b/pipeline/inputs/kernel-logs.md @@ -4,12 +4,14 @@ The _Kernel logs_ (`kmsg`) input plugin reads the Linux Kernel log buffer from t ## Configuration parameters +The plugin supports the following configuration parameters: + | Key | Description | Default | |:-------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------|:--------| -| `Prio_Level` | The log level to filter. The kernel log is dropped if its priority is more than `prio_level`. Allowed values are `0`-`8`. `8` means all logs are saved. | `8` | -| `Threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` | +| `prio_level` | The log level to filter. The kernel log is dropped if its priority is more than `prio_level`. Allowed values are `0`-`8`. `8` means all logs are saved. | `8` | +| `threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` | -## Get started +## Getting started To start getting the Linux Kernel messages, you can run the plugin from the command line or through the configuration file: