Merge pull request fluent#14 from nokute78/configure

configuration: add a description about filter

Author: edsiper

configuration/file.md

@@ -4,12 +4,14 @@ There are some cases where using the command line to start Fluent Bit is not ide
 
 Fluent Bit allows to use one configuration file which works at a global scope and uses the [schema](configuration_schema.md) defined previously.
 
-The configuration file support three types of sections:
+The configuration file supports four types of sections:
 
 - Service
 - Input
+- Filter
 - Output
 
+
 ## Service
 
 The _Service_ section defines global properties of the service, the keys available as of this version are described in the following table:
@@ -59,18 +61,40 @@ The following is an example of an _INPUT_ section:
     Tag  my_cpu
 ```
 
+## Filter
+
+A _FILTER_ section defines a filter (related to an filter plugin), here we will describe the base configuration for each _FILTER_ section. Note that each filter plugin may add it own configuration keys:
+
+| Key    | Description               |
+|--------|---------------------------|
+| Name   | Name of the filter plugin. |
+| Match  | It sets a pattern to match certain records Tag. It's case sensitive and support the start (*) character as a wildcard. | |
+
+
+The _Name_ is mandatory and it let Fluent Bit know which filter plugin should be loaded. The _Match_ is mandatory for all plugins.
+
+### Example
+
+The following is an example of an _FILTER_ section:
+
+```Python
+[FILTER]
+    Name  stdout
+    Match *
+```
+
 ## Output
 
 The _OUTPUT_ section specify a destination that certain records should follow after a Tag match. The configuration support the following keys:
 
 | Key    | Description                |
 |--------|----------------------------|
 | Name   | Name of the output plugin. |
-| Match  | It set a pattern to match certain records Tag. It's case sensitive and support the start (*) character as a wildcard. |
+| Match  | It sets a pattern to match certain records Tag. It's case sensitive and support the start (*) character as a wildcard. |
 
 ### Example
 
-The following is an example of an _INPUT_ section:
+The following is an example of an _OUTPUT_ section:
 
 ```Python
 [OUTPUT]