@@ -56,7 +56,7 @@ Config:
5656
5757- fields_from_labels (array[string], optional):
5858 A list of labels to pull is as fields. These are pulled in last and will
59- override any fields added from fields_from_env.
59+ override any fields added from fields_from_env.
6060- since_path (string, optional):
6161 Path to file where input will write a record of the "since" time for each
6262 container to be able to not miss log records while Heka is down (see
@@ -74,16 +74,16 @@ Config:
7474 since Heka has started will be re-fetched.
7575- container_expiry_days (int, optional):
7676 The number of days after which to remove unseen containers from the sinces
77- file. Defaults to 30 days. This prevents containers from building up
78- in the file forever. It has the effect of replaying logs from any container
79- which was not seen for this interval but then re-appears. Containers are
80- tracked by container ID.
77+ file. Defaults to 30 days. This prevents containers from building up
78+ in the file forever. It has the effect of replaying logs from any container
79+ which was not seen for this interval but then re-appears. Containers are
80+ tracked by container ID.
8181- new_containers_replay_logs (bool, optional):
8282 Will newly discovered containers replay all of the logs currently available
83- via the Docker logs endpoint? Defaults to true. If you are upgrading from
84- a previous version of heka, you may want to consider setting this to false
85- when first upgrading to prevent the massive replay of logs from all of
86- your existing containers.
83+ via the Docker logs endpoint? Defaults to true. If you are upgrading from
84+ a previous version of heka, you may want to consider setting this to false
85+ when first upgrading to prevent the massive replay of logs from all of
86+ your existing containers.
8787
8888Example:
8989
0 commit comments