the classifier alert also fires on an undecodable request and an unpublished reply
This commit is contained in:
parent
1c3551b030
commit
8847fa48c9
1 changed files with 26 additions and 17 deletions
|
|
@ -735,11 +735,13 @@ The classifier logs each run's result to its journal, which ships to
|
|||
VictoriaLogs like every swarm service container's
|
||||
([`services.md`](../../2-handbook/swarm/services.md#logs-victorialogs)).
|
||||
|
||||
A run that ends without a verdict logs `review classification run failed` at
|
||||
`warn`, with the cause in `F_ERROR`. The Grafana alert
|
||||
`hh-review-classifier-run-failed` fires on that line and keeps firing for 30
|
||||
minutes after the last one. It fires on a failed run, so a dead key with no PRs
|
||||
arriving stays quiet until the next PR.
|
||||
A run that ends without a verdict logs a `warn` line: `review classification
|
||||
run failed` with the cause in `F_ERROR`. A request that doesn't decode, and a
|
||||
reply the classifier can't encode or publish, each log a line of their own
|
||||
that names the error.
|
||||
The Grafana alert `hh-review-classifier-run-failed` fires on any of these and
|
||||
keeps firing for 30 minutes after the last one. It fires on a failed run, so a
|
||||
dead key with no PRs arriving stays quiet until the next PR.
|
||||
|
||||
## Still open
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue