Skip to content

Commit 486f777

Browse files
committed
Admin: config: classic: commands: final style
Signed-off-by: Lynette Miles <[email protected]>
1 parent 086ef29 commit 486f777

File tree

1 file changed

+5
-5
lines changed
  • administration/configuring-fluent-bit/classic-mode

1 file changed

+5
-5
lines changed

administration/configuring-fluent-bit/classic-mode/commands.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ Fluent Bit `Commands` extends a configuration file with specific built-in featur
66

77
| Command | Prototype | Description |
88
| :--- | :--- | :--- |
9-
| [`@INCLUDE`](commands.md#cmd_include) | `@INCLUDE FILE` | Include a configuration file. |
10-
| [`@SET`](commands.md#cmd_set) | `@SET KEY=VAL` | Set a configuration variable. |
9+
| [`@INCLUDE`](#include) | `@INCLUDE FILE` | Include a configuration file. |
10+
| [`@SET`](#set) | `@SET KEY=VAL` | Set a configuration variable. |
1111

12-
## `@INCLUDE` <a id="cmd_include"></a>
12+
## `@INCLUDE`
1313

1414
Configuring a logging pipeline might lead to an extensive configuration file. In order to maintain a human-readable configuration, split the configuration in multiple files.
1515

@@ -47,7 +47,7 @@ The following is an example of an `inputs.conf` file, like the one called in the
4747
Tag varlog.*
4848
```
4949

50-
### outputs.conf
50+
### `outputs.conf`
5151

5252
The following is an example of an `outputs.conf` file, like the one called in the previous example.
5353

@@ -64,7 +64,7 @@ The following is an example of an `outputs.conf` file, like the one called in th
6464
Logstash_Format On
6565
```
6666

67-
## `@SET` <a id="cmd_set"></a>
67+
## `@SET`
6868

6969
Fluent Bit supports [configuration variables](variables.md). One way to expose this variables to Fluent Bit is through setting a shell environment variable, the other is through the `@SET` command.
7070

0 commit comments

Comments
 (0)