Skip to content

Commit 247c171

Browse files
authored
Remove not existing FluentdQueueLengthBurst alert
FluentdQueueLengthBurst alert has been removed as of Cluster Logging v5.1. Remove not existing alert for suppressing confusion. Reference: https://bugzilla.redhat.com/show_bug.cgi?id=2083421
1 parent 05063f8 commit 247c171

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

modules/cluster-logging-collector-alerts.adoc

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,11 +23,6 @@ The following alerts are generated by the logging collector. You can view these
2323
|Fluentd is reporting that Prometheus could not scrape a specific Fluentd instance.
2424
|Critical
2525

26-
|`FluentdQueueLengthBurst`
27-
|`In the last minute, fluentd <instance> buffer queue length increased more than 32. Current value is <value>.`
28-
|Fluentd is reporting that it cannot keep up with the data being indexed.
29-
|Warning
30-
3126
|`FluentdQueueLengthIncreasing`
3227
|`In the last 12h, fluentd <instance> buffer queue length constantly increased more than 1. Current value is <value>.`
3328
|Fluentd is reporting that the queue size is increasing.

0 commit comments

Comments
 (0)