opendev/elastic-recheck
Code Issues Proposed changes

Document the INFO+ log level query restriction

Browse Source 
We only index on INFO and higher log level messages and sometimes the
only good thing to fingerprint in the logs is at DEBUG level, but that
won't work with elastic-recheck right now, so we have to document the
limitation.

Change-Id: I89fc35bca9f99ffdb1a0a71d88d041ac2215dd9d
This commit is contained in:
Matt Riedemann 2014-01-27 07:31:20 -08:00
parent 236a050be9
commit a59c39b067
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

@ -55,6 +55,10 @@ further down the stack that can cause many tempest tests to fail.
#. Given a transient bug that is seen during the gate, go through the
logs (logs.openstack.org) and try to find a log that is associated
with the failure. The closer to the root cause the better.
Note that queries can only be written against INFO level and higher log
messages. This is by design to not overwhelm the search cluster.
#. Go to logstash.openstack.org and create an elastic search query to
find the log message from step 1. To see the possible fields to
search on click on an entry. Lucene query syntax is available at