elastic-recheck/queries/1686542.yaml
Sorin Sbarnea c2c3f3a683 Identify *POST* timeout failures individually
Ability to identify only POST timeout failuse is critical because in
most cases this is an infra/ci related issue which has nothing to do
with the change itself.

As opposed to normal timeouts, this needs more attention from CI/infra
because almost for sure it means missing or partial logs.

Also changes original query so they would not overlap.

Change-Id: I3b112d4784c0f7dd57a26d08335c3cbe374eb90e
LogStash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22POST-RUN%20END%20RESULT_TIMED_OUT%5C%22%20AND%20tags%3A%20%5C%22console%5C%22%20AND%20voting%3A1
Related-Bug: 1807940
2018-12-27 16:00:19 +00:00

7 lines
202 B
YAML

query: >-
(message: "FAILED with status: 137" OR
message: "FAILED with status: 143" OR
message: "RUN END RESULT_TIMED_OUT") AND
NOT message:"POST-RUN END RESULT_TIMED_OUT" AND
tags: "console"