Skip to content

Commit

Permalink
Add documentation for filebeat.registry_flush (elastic#8785)
Browse files Browse the repository at this point in the history
Add documentation for filebeat.registry_flush to the filebeat reference configs docs and reference config file.
  • Loading branch information
Steffen Siering authored Nov 8, 2018
1 parent 5a38ccc commit 770b217
Show file tree
Hide file tree
Showing 3 changed files with 31 additions and 0 deletions.
6 changes: 6 additions & 0 deletions filebeat/_meta/common.reference.p2.yml
Original file line number Diff line number Diff line change
Expand Up @@ -389,6 +389,12 @@ filebeat.inputs:
# This option is not supported on Windows.
#filebeat.registry_file_permissions: 0600

# The timeout value that controls when registry entries are written to disk
# (flushed). When an unwritten update exceeds this value, it triggers a write to
# disk. When registry_flush is set to 0s, the registry is written to disk after
# each batch of events has been published successfully. The default value is 0s.
#filebeat.registry_flush: 0s

# By default Ingest pipelines are not updated if a pipeline with the same ID
# already exists. If this option is enabled Filebeat overwrites pipelines
# everytime a new Elasticsearch connection is established.
Expand Down
19 changes: 19 additions & 0 deletions filebeat/docs/filebeat-general-options.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,25 @@ Examples:
filebeat.registry_file_permissions: 0600
-------------------------------------------------------------------------------------

[float]
==== `registry_flush`


The timeout value that controls when registry entries are written to disk
(flushed). When an unwritten update exceeds this value, it triggers a write to
disk. When registry_flush is set to 0s, the registry is written to disk after
each batch of events has been published successfully. The default value is 0s.

NOTE: The registry is always updated when Filebeat shuts down normally. After an
abnormal shutdown, the registry will not be up-to-date if the registry_flush
value is >0s. Filebeat will send published events again (depending on values in
the last updated registry file).

NOTE: Filtering out a huge number of logs can cause many registry updates, slowing
down processing. Setting registry_flush to a value >0s reduces write operations,
helping Filebeat process more events.


[float]
==== `config_dir`

Expand Down
6 changes: 6 additions & 0 deletions filebeat/filebeat.reference.yml
Original file line number Diff line number Diff line change
Expand Up @@ -757,6 +757,12 @@ filebeat.inputs:
# This option is not supported on Windows.
#filebeat.registry_file_permissions: 0600

# The timeout value that controls when registry entries are written to disk
# (flushed). When an unwritten update exceeds this value, it triggers a write to
# disk. When registry_flush is set to 0s, the registry is written to disk after
# each batch of events has been published successfully. The default value is 0s.
#filebeat.registry_flush: 0s

# By default Ingest pipelines are not updated if a pipeline with the same ID
# already exists. If this option is enabled Filebeat overwrites pipelines
# everytime a new Elasticsearch connection is established.
Expand Down

0 comments on commit 770b217

Please sign in to comment.