You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -253,14 +253,14 @@ Please consider updating Fluentd if you are using any version older than Fluentd
253
253
254
254
## Feature
255
255
256
-
`tailcheck` performs the following checks on the specified pos file.
256
+
`fluent-tailcheck` performs the following checks on the specified pos file.
257
257
258
258
* duplication check
259
259
* collection ratio check
260
260
261
261
### Duplication check
262
262
263
-
`tailcheck` checks whether there is any dulication in the specified pos files.
263
+
`fluent-tailcheck` checks whether there is any dulication in the specified pos files.
264
264
265
265
The keys of watching pos entries in one pos file must be unique.
266
266
@@ -276,9 +276,9 @@ Especially, the following log missing issue causes this duplication.
276
276
277
277
### Collection ratio check
278
278
279
-
`tailcheck` checks collection ratio of each watching pos entry.
279
+
`fluent-tailcheck` checks collection ratio of each watching pos entry.
280
280
281
-
By default, `tailcheck` detects log files that have not been collected up to 50% of the filesize.
281
+
By default, `fluent-tailcheck` detects log files that have not been collected up to 50% of the filesize.
282
282
You can change this threshold by `--ratio` option.
283
283
Please see `Usage` section for details.
284
284
@@ -293,12 +293,12 @@ Especially, if the `in_tail` uses [follow_inodes](https://docs.fluentd.org/input
293
293
294
294
#### Limitation
295
295
296
-
`tailcheck` checks the sizes of logfiles based on the paths recorded in the pos files (except already unwatched pos entries).
296
+
`fluent-tailcheck` checks the sizes of logfiles based on the paths recorded in the pos files (except already unwatched pos entries).
297
297
298
298
However, if using `--follow-inodes`, there is a restriction on which files can be checked.
299
-
If using `--follow-inodes`, it is possible that `tailcheck` can not check the already rotated logfiles even if they are recorded in the pos files and are not unwatched yet.
299
+
If using `--follow-inodes`, it is possible that `fluent-tailcheck` can not check the already rotated logfiles even if they are recorded in the pos files and are not unwatched yet.
300
300
Since the path recorded in the pos file is not updated after log rotation, the current path and inode may differ.
301
-
`tailcheck` checks only log files whose path and inode in the pos file match.
301
+
`fluent-tailcheck` checks only log files whose path and inode in the pos file match.
302
302
At least, it can check the current log files.
303
303
304
304
If not using `--follow-inodes`, this limitation does not exist.
@@ -309,9 +309,9 @@ If not using `--follow-inodes`, this limitation does not exist.
0 commit comments