opendev
/
elastic-recheck
Code Issues Proposed changes
Classify tempest-devstack failures using ElasticSearch
24 Commits 2 Branches 0 Tags 14 MiB
Python 53.3%
JavaScript 38.1%
HTML 7.5%
Makefile 0.5%
CSS 0.4%
Other 0.2%
Go to file
Matthew c30528d1f1 Add irc bot support to elasticRecheck 2013-09-17 00:27:14 -04:00
tests Add test and a sleep 2013-09-14 08:54:33 -07:00
.gitignore Add dot files 2013-09-13 00:49:28 -07:00
.testr.conf Add dot files 2013-09-13 00:49:28 -07:00
LICENSE First commit, including proof of concept ElasticSearch tool 2013-09-12 16:54:27 -07:00
README.md Add irc bot support to elasticRecheck 2013-09-17 00:27:14 -04:00
bot.py Add irc bot support to elasticRecheck 2013-09-17 00:27:14 -04:00
elasticRecheck.conf Add irc bot support to elasticRecheck 2013-09-17 00:27:14 -04:00
elasticRecheck.py Add irc bot support to elasticRecheck 2013-09-17 00:27:14 -04:00
proof_of_concept.py Add reqs file 2013-09-12 17:01:32 -07:00
queries.json better 1191960 query 2013-09-16 15:25:25 -07:00
recheckwatchbot.yaml Add irc bot support to elasticRecheck 2013-09-17 00:27:14 -04:00
requirements.txt Add irc bot support to elasticRecheck 2013-09-17 00:27:14 -04:00

README.md

elasticRecheck

Classify tempest-devstack failures using a list of elastic search queries.

Idea

When a tempest job failure is detected, by monitoring gerrit (using gerritlib), a collection of logstash queries will be run on the failed job to detect what the bug was.

Eventually this can be tied into the rechecker tool and launchpad

Future Work

  • Pull in list of queries from a more flexible source, so a commit isn't needed to update each time
  • Turn into a server app
  • Make unit tests robust and not need internet

Dependencies

  • gerritlib
  • pyelasticsearch