Adding YAML examples and standardizing shell usage for Windows Event Log (winevtlog) input plugin, part of issue #1859.

Signed-off-by: Eric D. Schabell <[email protected]>

Author: eschabell

pipeline/inputs/windows-event-log-winevtlog.md

@@ -34,8 +34,24 @@ Note that if you do not set _db_, the plugin will tail channels on each startup.
 Here is a minimum configuration example.
 
 {% tabs %}
+{% tab title="fluent-bit.yaml" %}
+
+```yaml
+pipeline:
+    inputs:
+      - name: winevtlog
+        channels: Setup,Windows PowerShell
+        interval_sec: 1
+        db: winevtlog.sqllite
+    outputs:
+      - name: stdout
+        match: '*'
+```
+
+{% endtab %}
 {% tab title="fluent-bit.conf" %}
-```python
+
+```text
 [INPUT]
     Name         winevtlog
     Channels     Setup,Windows PowerShell
@@ -46,20 +62,7 @@ Here is a minimum configuration example.
     Name   stdout
     Match  *
 ```
-{% endtab %}
 
-{% tab title="fluent-bit.yaml" %}
-```yaml
-pipeline:
-  inputs:
-    - name: winevtlog
-      channels: Setup,Windows PowerShell
-      interval_sec: 1
-      db: winevtlog.sqllite
-  outputs:
-    - name: stdout
-      match: '*'
-```
 {% endtab %}
 {% endtabs %}
 
@@ -79,9 +82,9 @@ For further details, please refer to [the MSDN doc](https://learn.microsoft.com/
 
 If you want to do a quick test, you can run this plugin from the command line.
 
-```bash
-$ fluent-bit -i winevtlog -p 'channels=Setup' -p 'Read_Existing_Events=true' -o stdout
+```shell
+$ ./fluent-bit -i winevtlog -p 'channels=Setup' -p 'Read_Existing_Events=true' -o stdout
 ```
 
 Note that `winevtlog` plugin will tail channels on each startup.
-If you want to confirm whether this plugin is working or not, you should specify `-p 'Read_Existing_Events=true'` parameter.
+If you want to confirm whether this plugin is working or not, you should specify `-p 'Read_Existing_Events=true'` parameter.