Skip to content

Commit

Permalink
Fix storage.metrics option to be enabled by default
Browse files Browse the repository at this point in the history
Signed-off-by: motohiro.nakamura <motohiro.nakamura@lycorp.co.jp>
  • Loading branch information
GarupanOjisan committed Jun 28, 2024
1 parent 397a33a commit 4020377
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion administration/buffering-and-storage.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ The Service section refers to the section defined in the main [configuration fil
| storage.checksum | Enable the data integrity check when writing and reading data from the filesystem. The storage layer uses the CRC32 algorithm. | Off |
| storage.max\_chunks\_up | If the input plugin has enabled `filesystem` storage type, this property sets the maximum number of Chunks that can be `up` in memory. *This is the setting to use to control memory usage when you enable `storage.type filesystem`*. | 128 |
| storage.backlog.mem\_limit | If _storage.path_ is set, Fluent Bit will look for data chunks that were not delivered and are still in the storage layer, these are called _backlog_ data. _Backlog chunks_ are filesystem chunks that were left over from a previous Fluent Bit run; chunks that could not be sent before exit that Fluent Bit will pick up when restarted. Fluent Bit will check the `storage.backlog.mem_limit` value against the current memory usage from all `up` chunks for the input. If the `up` chunks currently consume less memory than the limit, it will bring the _backlog_ chunks up into memory so they can be sent by outputs. | 5M |
| storage.metrics | If `http_server` option has been enabled in the main `[SERVICE]` section, this option registers a new endpoint where internal metrics of the storage layer can be consumed. For more details refer to the [Monitoring](monitoring.md) section. | off |
| storage.metrics | If `http_server` option has been enabled in the main `[SERVICE]` section, this option registers a new endpoint where internal metrics of the storage layer can be consumed. For more details refer to the [Monitoring](monitoring.md) section. | On |
| storage.delete_irrecoverable_chunks | When enabled, [irrecoverable chunks](./buffering-and-storage.md#irrecoverable-chunks) will be deleted during runtime, and any other irrecoverable chunk located in the configured storage path directory will be deleted when Fluent-Bit starts. | Off |

a Service section will look like this:
Expand Down

0 comments on commit 4020377

Please sign in to comment.