Alert NoOutputBytesProcessed should combine outputs #640
Conversation
|
1 similar comment
|
edsiper
added
the
waiting-for-user
|
Hi, @MPV would you mind reviewing the last comment? |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
MPV
force-pushed
the
patch-1
branch
2 times, most recently
from
e800815 to
bd67bc2
Compare
We were seeing issues where we got alerted due to some outputs not sending data for more than 15 minutes. For example, this is expected from journald logs on worker nodes in a cluster, thus this adjustment to the alert. We now aggregate output per pod and alert if no bytes are sent for 15 minutes. Signed-off-by: Victor Sollerhed <victor.sollerhed@pagero.com>
|
@lecaros could you review this again? commit has been signed now. |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
@edsiper, interested in this change? Happy to close it if not useful as-is.😊 |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
eschabell
added
waiting-on-review
|
Reviewed. |
|
@MPV picking up the docs PR work, merging this one, thanks for the patience. |
We were seeing issues where we got alerted due to some outputs not sending data for more than 15 minutes. For example, this is expected from journald logs on worker nodes in a cluster, thus this adjustment to the alert. We now aggregate output per pod and alert if no bytes are sent for 15 minutes. Signed-off-by: Victor Sollerhed <victor.sollerhed@pagero.com> Signed-off-by: Tom <yao.lin@siemens.com>
4 participants
We were seeing issues where we got alerted due to some outputs not sending data for more than 15 minutes.
For example, this is expected from journald logs on worker nodes in a cluster, thus this adjustment to the alert.
We now aggregate output per pod and alert if no bytes are sent for 15 minutes.