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
* The command has checked 2 entries for duplication check.
180
+
* The command has checked 2 pos entries for duplication check.
181
181
* The command has checked 2 files for collection ratio check.
182
182
* There is no anomalies.
183
183
184
184
#### Pos duplication found
185
185
186
186
```
187
187
Check /path/to/pos.
188
-
Checked duplicated pos for 3 PosEntries.
189
-
Duplicated PosEntries are found. This is a known log loss issue that was fixed in Fluentd v1.16.3.
190
-
Duplicated keys:
188
+
Done duplication check for 3 PosEntries.
189
+
Duplicated PosEntries are found. This is a known log missing issue that was fixed in Fluentd v1.16.3 (fluent-package v5.0.2, td-agent v4.5.2). If you are using any version older than these, updating Fluentd will resolve the issue.
190
+
Duplicated paths:
191
191
/test/foo.log
192
-
Checked collection ratio of 0 files.
192
+
Done collection ratio check for 0 files.
193
193
194
194
All check completed.
195
195
Some anomalies are found. Please check whether there is any log loss.
196
196
```
197
197
198
-
In this case, some keys of the pos entries are duplicated.
198
+
In this case, some the pos entries are duplicated.
199
199
It is a known log missing issue that was fixed in Fluentd v1.16.3.
200
200
201
201
> *https://github.com/fluent/fluentd/issues/3614
202
202
> * In case `follow_inodes false` (default setting), collection of a file may stop and continue to stop after log rotation.
203
203
> * Fixed since Fluentd v1.16.3 (fluent-package v5.0.2, td-agent v4.5.2).
204
204
205
-
So, you should check whether there is any log missing, and consider updating, especially, if your version is before Fluentd v1.16.3 (fluent-package v5.0.2, td-agent v4.5.2).
205
+
So, you should check whether there is any log missing, and consider updating Fluentd, especially, if you are using any version older than Fluentd v1.16.3 (fluent-package v5.0.2, td-agent v4.5.2).
206
206
207
207
#### Too low collection ratio file found
208
208
209
209
```
210
210
Check /path/to/pos.
211
-
Checked duplicated pos for 2 PosEntries.
212
-
Checked collection ratio of 2 files.
213
-
Collection ratio of some files are too low. Collection of those files may have stopped or may not be keeping up.
211
+
Done duplication check for 2 PosEntries.
212
+
Done collection ratio check for 2 files.
213
+
Collection ratio of some files are too low. Collection of those files may not be keeping up. Or it may have stopped with some anomalies. This can be a known log missing issue of the follow_inodes feature that was fixed in Fluentd v1.16.2 (fluent-package v5.0.0, td-agent v4.5.1). If you are using any version older than these, updating Fluentd will resolve the issue.
214
214
Filepaths with too low collection ratio (threshold: 0.8):
215
215
/test/bar.log (ratio: 0.7)
216
216
/test/foo.log (ratio: 0.7)
@@ -234,8 +234,7 @@ Especially, if the `in_tail` uses [follow_inodes](https://docs.fluentd.org/input
234
234
> * In case `follow_inodes true`, collection of a file may stop and continue to stop after log rotation.
235
235
> * Fixed since Fluentd v1.16.2 (fluent-package v5.0.0, td-agent v4.5.1).
236
236
237
-
If this issue is occurring, this too low collection ratio is detected.
238
-
In that case, please consider updating if your version is before Fluentd v1.16.2 (td-agent v4.5.1).
237
+
Please consider updating Fluentd if you are using any version older than Fluentd v1.16.2 (td-agent v4.5.1).
puts"Collection ratio of some files are too low. Collection of those files may have stopped or may not be keeping up."
100
99
if@follow_inodes
101
-
puts"This can be a known log loss issue of the follow_inodes feature that was fixed in Fluentd v1.16.2."
100
+
puts"Collection ratio of some files are too low. Collection of those files may not be keeping up. Or it may have stopped with some anomalies. This can be a known log missing issue of the follow_inodes feature that was fixed in Fluentd v1.16.2 (fluent-package v5.0.0, td-agent v4.5.1). If you are using any version older than these, updating Fluentd will resolve the issue."
101
+
else
102
+
puts"Collection ratio of some files are too low. Collection of those files may not be keeping up. Or it may have stopped with some anomalies. It is recommended to verify whether there is any log missing."
102
103
end
103
104
104
105
puts"Filepaths with too low collection ratio (threshold: #{@collection_ratio_threshold}):"
Copy file name to clipboardExpand all lines: lib/fluent/tail_checker/duplicated_pos_checker.rb
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ def check
40
40
duplicated_key_set.add(key)
41
41
end
42
42
43
-
puts"Checked duplicated pos for #{checked_key_counts} PosEntries."
43
+
puts"Done duplication check for #{checked_key_counts} PosEntries."
44
44
45
45
ifduplicated_key_found
46
46
log_issue(duplicated_key_set)
@@ -52,12 +52,13 @@ def check
52
52
53
53
deflog_issue(duplicated_keys)
54
54
if@follow_inodes
55
-
puts"Duplicated PosEntries are found with follow_inodes. Unknown anomalies may be occurring."
55
+
puts"Duplicated PosEntries are found. Unknown anomalies may be occurring. It is recommended to verify whether there is any log missing."
56
+
puts"Duplicated inodes:"
56
57
else
57
-
puts"Duplicated PosEntries are found. This is a known log loss issue that was fixed in Fluentd v1.16.3."
58
+
puts"Duplicated PosEntries are found. This is a known log missing issue that was fixed in Fluentd v1.16.3 (fluent-package v5.0.2, td-agent v4.5.2). If you are using any version older than these, updating Fluentd will resolve the issue."
0 commit comments