opendev/elastic-recheck
Code Issues Proposed changes

Identify *POST* timeout failures individually

Browse Source 
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
This commit is contained in:
Sorin Sbarnea 2018-12-17 12:03:04 +00:00
parent b9146d923f
commit c2c3f3a683
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
queries/1686542.yaml
View File

@ -2,4 +2,5 @@ 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"

3
queries/1807940.yaml Normal file
View File

@ -0,0 +1,3 @@
query: >-
message: "POST-RUN END RESULT_TIMED_OUT" AND
tags: "console"