Skip to content

Commit f416a90

Browse files
eschabelleschabell
authored
Input plugins standardized code indentation and table formatting fixed. Fixes #1954 (#1956)
* Fixed code indents for examples in CollectD input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples in CPU log based metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples in Disk I/O log based metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples in Docker events input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples inDocker log based metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples in Dummy input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples in Ebpf input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples in Elasticsearch input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table format in Exec input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed table formatting to markdown standards for collectd intput plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed table formatting to markdown standards for cpu metrics intput plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed table formatting to markdown standards for disk io log based metrics intput plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed table formatting to markdown standards for docker events intput plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed table formatting to markdown standards for docker log based metrics intput plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed table formatting to markdown standards for dummy intput plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed table formatting to markdown standards for elasticsearch intput plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed table formatting to markdown standards for exec wasi intput plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Fluent Bit Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Forward input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Head input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Health input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in HTTP input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Kafka input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Kernel Log input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Kubernetes Events input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Memory Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in MQTT input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Network I/O Log Based Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in NGINX input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in NGINX input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Node Exporter Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in OpenTelemtry input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Podman Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Process Log Based Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Process Exporter Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Prometheus Remote Write input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Prometheus Scrape Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Random input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Serial Interface input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Splunk input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Standard Input input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in StatsD input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Syslog input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Systemd input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Tail input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in TCP input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Thermal input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in UDP input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Windows Event Log input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Windows Event Log (winevtlog) input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Windows Exporter Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed shell useage in EBPF input plugin doc. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> * Fixed code indents for examples and table formatting in Windows Exporter Metrics input plugin. Part of issue #1954. Signed-off-by: Eric D. Schabell <[email protected]> --------- Signed-off-by: Eric D. Schabell <[email protected]>
1 parent 931a442 commit f416a90

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

43 files changed

+1586
-1903
lines changed

‎pipeline/inputs/collectd.md

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ The _Collectd_ input plugin lets you receive datagrams from the `collectd` servi
66

77
The plugin supports the following configuration parameters:
88

9-
| Key | Description | Default |
10-
| :--- | :--- | :--- |
11-
| `Listen` | Set the address to listen to. | `0.0.0.0` |
12-
| `Port` | Set the port to listen to. | `25826` |
13-
| `TypesDB` | Set the data specification file. | `/usr/share/collectd/types.db` |
14-
| `Threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` |
9+
| Key | Description | Default |
10+
|:-----------|:--------------------------------------------------------------------------------------------------------|:-------------------------------|
11+
| `Listen` | Set the address to listen to. | `0.0.0.0` |
12+
| `Port` | Set the port to listen to. | `25826` |
13+
| `TypesDB` | Set the data specification file. | `/usr/share/collectd/types.db` |
14+
| `Threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` |
1515

1616
## Configuration examples
1717

@@ -22,30 +22,30 @@ Here is a basic configuration example:
2222

2323
```yaml
2424
pipeline:
25-
inputs:
26-
- name: collectd
27-
listen: 0.0.0.0
28-
port: 25826
29-
typesdb: '/user/share/collectd/types.db,/etc/collectd/custom.db'
30-
31-
outputs:
32-
- name: stdout
33-
match: '*'
25+
inputs:
26+
- name: collectd
27+
listen: 0.0.0.0
28+
port: 25826
29+
typesdb: '/user/share/collectd/types.db,/etc/collectd/custom.db'
30+
31+
outputs:
32+
- name: stdout
33+
match: '*'
3434
```
3535
3636
{% endtab %}
3737
{% tab title="fluent-bit.conf" %}
3838
3939
```text
4040
[INPUT]
41-
Name collectd
42-
Listen 0.0.0.0
43-
Port 25826
44-
TypesDB /usr/share/collectd/types.db,/etc/collectd/custom.db
41+
Name collectd
42+
Listen 0.0.0.0
43+
Port 25826
44+
TypesDB /usr/share/collectd/types.db,/etc/collectd/custom.db
4545

4646
[OUTPUT]
47-
Name stdout
48-
Match *
47+
Name stdout
48+
Match *
4949
```
5050

5151
{% endtab %}

‎pipeline/inputs/cpu-metrics.md

Lines changed: 28 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -6,30 +6,30 @@ The following tables describe the information generated by the plugin. The follo
66

77
The CPU metrics plugin creates metrics that are log-based, such as JSON payload. For Prometheus-based metrics, see the _Node Exporter Metrics_ input plugin.
88

9-
| Key | Description |
10-
| :--- | :--- |
11-
| `cpu_p` | CPU usage of the overall system, this value is the summation of time spent on user and kernel space. The result takes in consideration the numbers of CPU cores in the system. |
12-
| `user_p` | CPU usage in User mode, for short it means the CPU usage by user space programs. The result of this value takes in consideration the numbers of CPU cores in the system. |
13-
| `system_p` | CPU usage in Kernel mode, for short it means the CPU usage by the Kernel. The result of this value takes in consideration the numbers of CPU cores in the system. |
14-
| `threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). Default: `false`. |
9+
| Key | Description |
10+
|:-----------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
11+
| `cpu_p` | CPU usage of the overall system, this value is the summation of time spent on user and kernel space. The result takes in consideration the numbers of CPU cores in the system. |
12+
| `user_p` | CPU usage in User mode, for short it means the CPU usage by user space programs. The result of this value takes in consideration the numbers of CPU cores in the system. |
13+
| `system_p` | CPU usage in Kernel mode, for short it means the CPU usage by the Kernel. The result of this value takes in consideration the numbers of CPU cores in the system. |
14+
| `threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). Default: `false`. |
1515

1616
In addition to the keys reported in the previous table, a similar content is created per CPU core. The cores are listed from `0` to `N` as the Kernel reports:
1717

18-
| Key | Description |
19-
| :--- | :--- |
20-
| `cpuN.p_cpu` | Represents the total CPU usage by core `N`. |
21-
| `cpuN.p_user` | Total CPU spent in user mode or user space programs associated to this core. |
22-
| `cpuN.p_system` | Total CPU spent in system or kernel mode associated to this core. |
18+
| Key | Description |
19+
|:----------------|:-----------------------------------------------------------------------------|
20+
| `cpuN.p_cpu` | Represents the total CPU usage by core `N`. |
21+
| `cpuN.p_user` | Total CPU spent in user mode or user space programs associated to this core. |
22+
| `cpuN.p_system` | Total CPU spent in system or kernel mode associated to this core. |
2323

2424
## Configuration parameters
2525

2626
The plugin supports the following configuration parameters:
2727

28-
| Key | Description | Default |
29-
| :--- | :--- | :--- |
30-
| `Interval_Sec` | Polling interval in seconds. | `1` |
31-
| `Interval_NSec | Polling interval in nanoseconds` | `0` |
32-
| `PID` | Specify the `ID` (`PID`) of a running process in the system. By default, the plugin monitors the whole system but if this option is set, it will only monitor the given process ID. | _none_ |
28+
| Key | Description | Default |
29+
|:---------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------|
30+
| `Interval_Sec` | Polling interval in seconds. | `1` |
31+
| `Interval_NSec | Polling interval in nanoseconds` | `0` |
32+
| `PID` | Specify the `ID` (`PID`) of a running process in the system. By default, the plugin monitors the whole system but if this option is set, it will only monitor the given process ID. | _none_ |
3333

3434
## Get started
3535

@@ -46,17 +46,12 @@ build/bin/fluent-bit -i cpu -t my_cpu -o stdout -m '*'
4646
The command returns results similar to the following:
4747

4848
```text
49-
Fluent Bit v1.x.x
50-
* Copyright (C) 2019-2020 The Fluent Bit Authors
51-
* Copyright (C) 2015-2018 Treasure Data
52-
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
53-
* https://fluentbit.io
54-
55-
[2019/09/02 10:46:29] [ info] starting engine
49+
...
5650
[0] [1452185189, {"cpu_p"=>7.00, "user_p"=>5.00, "system_p"=>2.00, "cpu0.p_cpu"=>10.00, "cpu0.p_user"=>8.00, "cpu0.p_system"=>2.00, "cpu1.p_cpu"=>6.00, "cpu1.p_user"=>4.00, "cpu1.p_system"=>2.00}]
5751
[1] [1452185190, {"cpu_p"=>6.50, "user_p"=>5.00, "system_p"=>1.50, "cpu0.p_cpu"=>6.00, "cpu0.p_user"=>5.00, "cpu0.p_system"=>1.00, "cpu1.p_cpu"=>7.00, "cpu1.p_user"=>5.00, "cpu1.p_system"=>2.00}]
5852
[2] [1452185191, {"cpu_p"=>7.50, "user_p"=>5.00, "system_p"=>2.50, "cpu0.p_cpu"=>7.00, "cpu0.p_user"=>3.00, "cpu0.p_system"=>4.00, "cpu1.p_cpu"=>6.00, "cpu1.p_user"=>6.00, "cpu1.p_system"=>0.00}]
5953
[3] [1452185192, {"cpu_p"=>4.50, "user_p"=>3.50, "system_p"=>1.00, "cpu0.p_cpu"=>6.00, "cpu0.p_user"=>5.00, "cpu0.p_system"=>1.00, "cpu1.p_cpu"=>5.00, "cpu1.p_user"=>3.00, "cpu1.p_system"=>2.00}]
54+
...
6055
```
6156

6257
As described previously, the CPU input plugin gathers the overall usage every one second and flushed the information to the output on the fifth second. This example uses the `stdout` plugin to demonstrate the output records. In a real use-case you might want to flush this information to some central aggregator such as [Fluentd](http://fluentd.org) or [Elasticsearch](http://elastic.co).
@@ -71,26 +66,26 @@ In your main configuration file append the following:
7166
```yaml
7267

7368
pipeline:
74-
inputs:
75-
- name: cpu
76-
tag: my_cpu
69+
inputs:
70+
- name: cpu
71+
tag: my_cpu
7772

78-
outputs:
79-
- name: stdout
80-
match: '*'
73+
outputs:
74+
- name: stdout
75+
match: '*'
8176
```
8277
8378
{% endtab %}
8479
{% tab title="fluent-bit.conf" %}
8580
8681
```shell
8782
[INPUT]
88-
Name cpu
89-
Tag my_cpu
83+
Name cpu
84+
Tag my_cpu
9085

9186
[OUTPUT]
92-
Name stdout
93-
Match *
87+
Name stdout
88+
Match *
9489
```
9590

9691
{% endtab %}

‎pipeline/inputs/disk-io-metrics.md

Lines changed: 23 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,12 @@ The _Disk I/O metrics_ plugin creates metrics that are log-based, such as JSON p
88

99
The plugin supports the following configuration parameters:
1010

11-
| Key | Description | Default |
12-
| :--- | :--- | :--- |
13-
| `Interval_Sec` | Polling interval (seconds). | `1` |
14-
| `Interval_NSec` | Polling interval (nanosecond). | `0` |
15-
| `Dev_Name` | Device name to limit the target (for example, `sda`). If not set, `in_disk` gathers information from all of disks and partitions. | all disks |
16-
| `Threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` |
11+
| Key | Description | Default |
12+
|:----------------|:----------------------------------------------------------------------------------------------------------------------------------|:----------|
13+
| `Interval_Sec` | Polling interval (seconds). | `1` |
14+
| `Interval_NSec` | Polling interval (nanosecond). | `0` |
15+
| `Dev_Name` | Device name to limit the target (for example, `sda`). If not set, `in_disk` gathers information from all of disks and partitions. | all disks |
16+
| `Threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` |
1717

1818
## Get started
1919

@@ -30,17 +30,12 @@ fluent-bit -i disk -o stdout
3030
Which returns information like the following:
3131

3232
```text
33-
Fluent Bit v1.x.x
34-
* Copyright (C) 2019-2020 The Fluent Bit Authors
35-
* Copyright (C) 2015-2018 Treasure Data
36-
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
37-
* https://fluentbit.io
38-
39-
[2017/01/28 16:58:16] [ info] [engine] started
33+
...
4034
[0] disk.0: [1485590297, {"read_size"=>0, "write_size"=>0}]
4135
[1] disk.0: [1485590298, {"read_size"=>0, "write_size"=>0}]
4236
[2] disk.0: [1485590299, {"read_size"=>0, "write_size"=>0}]
4337
[3] disk.0: [1485590300, {"read_size"=>0, "write_size"=>11997184}]
38+
...
4439
```
4540

4641
### Configuration file
@@ -52,30 +47,30 @@ In your main configuration file append the following:
5247

5348
```yaml
5449
pipeline:
55-
inputs:
56-
- name: disk
57-
tag: disk
58-
interval_sec: 1
59-
interval_nsec: 0
60-
61-
outputs:
62-
- name: stdout
63-
match: '*'
50+
inputs:
51+
- name: disk
52+
tag: disk
53+
interval_sec: 1
54+
interval_nsec: 0
55+
56+
outputs:
57+
- name: stdout
58+
match: '*'
6459
```
6560
6661
{% endtab %}
6762
{% tab title="fluent-bit.conf" %}
6863
6964
```text
7065
[INPUT]
71-
Name disk
72-
Tag disk
73-
Interval_Sec 1
74-
Interval_NSec 0
66+
Name disk
67+
Tag disk
68+
Interval_Sec 1
69+
Interval_NSec 0
7570

7671
[OUTPUT]
77-
Name stdout
78-
Match *
72+
Name stdout
73+
Match *
7974
```
8075

8176
{% endtab %}

‎pipeline/inputs/docker-events.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,15 @@ The _Docker events_ input plugin uses the Docker API to capture server events. A
66

77
This plugin supports the following configuration parameters:
88

9-
| Key | Description | Default |
10-
| :--- | :--- | :--- |
11-
| `Unix_Path` | The docker socket Unix path. | `/var/run/docker.sock` |
12-
| `Buffer_Size` | The size of the buffer used to read docker events in bytes. | `8192` |
13-
| `Parser` | Specify the name of a parser to interpret the entry as a structured message. | _none_ |
14-
| `Key` | When a message is unstructured (no parser applied), it's appended as a string under the key name `message`. | `message` |
15-
| `Reconnect.Retry_limits`| The maximum number of retries allowed. The plugin tries to reconnect with docker socket when `EOF` is detected. | `5` |
16-
| `Reconnect.Retry_interval`| The retry interval in seconds. | `1` |
17-
| `Threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` |
9+
| Key | Description | Default |
10+
|:---------------------------|:----------------------------------------------------------------------------------------------------------------|:-----------------------|
11+
| `Unix_Path` | The docker socket Unix path. | `/var/run/docker.sock` |
12+
| `Buffer_Size` | The size of the buffer used to read docker events in bytes. | `8192` |
13+
| `Parser` | Specify the name of a parser to interpret the entry as a structured message. | _none_ |
14+
| `Key` | When a message is unstructured (no parser applied), it's appended as a string under the key name `message`. | `message` |
15+
| `Reconnect.Retry_limits` | The maximum number of retries allowed. The plugin tries to reconnect with docker socket when `EOF` is detected. | `5` |
16+
| `Reconnect.Retry_interval` | The retry interval in seconds. | `1` |
17+
| `Threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` |
1818

1919
### Command line
2020

@@ -33,24 +33,24 @@ In your main configuration file append the following:
3333

3434
```yaml
3535
pipeline:
36-
inputs:
37-
- name: docker_events
36+
inputs:
37+
- name: docker_events
3838

39-
outputs:
40-
- name: stdout
41-
match: '*'
39+
outputs:
40+
- name: stdout
41+
match: '*'
4242
```
4343
4444
{% endtab %}
4545
{% tab title="fluent-bit.conf" %}
4646
4747
```text
4848
[INPUT]
49-
Name docker_events
49+
Name docker_events
5050

5151
[OUTPUT]
52-
Name stdout
53-
Match *
52+
Name stdout
53+
Match *
5454
```
5555

5656
{% endtab %}

‎pipeline/inputs/docker-metrics.md

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ The _Docker_ input plugin you collect Docker container metrics, including memory
66

77
The plugin supports the following configuration parameters:
88

9-
| Key | Description | Default |
10-
| ------------ | ----------------------------------------------- | ------- |
11-
| `Interval_Sec` | Polling interval in seconds | `1` |
12-
| `Include` | A space-separated list of containers to include. | _none_ |
13-
| `Exclude` | A space-separated list of containers to exclude. | _none_ |
14-
| `Threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` |
15-
| `path.containers` | Used to specify the container directory if Docker is configured with a custom `data-root` directory. | `/var/lib/docker/containers` |
9+
| Key | Description | Default |
10+
|-------------------|---------------------------------------------------------------------------------------------------------|------------------------------|
11+
| `Interval_Sec` | Polling interval in seconds | `1` |
12+
| `Include` | A space-separated list of containers to include. | _none_ |
13+
| `Exclude` | A space-separated list of containers to exclude. | _none_ |
14+
| `Threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` |
15+
| `path.containers` | Used to specify the container directory if Docker is configured with a custom `data-root` directory. | `/var/lib/docker/containers` |
1616

1717
If you set neither `Include` nor `Exclude`, the plugin will try to get metrics from all running containers.
1818

@@ -25,25 +25,26 @@ The following example configuration collects metrics from two docker instances (
2525

2626
```yaml
2727
pipeline:
28-
inputs:
29-
- name: docker
30-
include: 6bab19c3a0f9 14159be4ca2c
28+
inputs:
29+
- name: docker
30+
include: 6bab19c3a0f9 14159be4ca2c
3131

32-
outputs:
33-
- name: stdout
34-
match: '*'
32+
outputs:
33+
- name: stdout
34+
match: '*'
3535
```
3636
3737
{% endtab %}
3838
{% tab title="fluent-bit.conf" %}
3939
4040
```text
4141
[INPUT]
42-
Name docker
43-
Include 6bab19c3a0f9 14159be4ca2c
42+
Name docker
43+
Include 6bab19c3a0f9 14159be4ca2c
44+
4445
[OUTPUT]
45-
Name stdout
46-
Match *
46+
Name stdout
47+
Match *
4748
```
4849

4950
{% endtab %}

0 commit comments

Comments
 (0)