opendev
/
elastic-recheck
Code Issues Proposed changes
Classify tempest-devstack failures using ElasticSearch
32 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 Treinish 545012839a Make bot.py behave like a daemon 
This includes a number of changes to prevent printing to stdout and
enable using daemonContext so that we can run bot.py as a daemon.
 		2013-09-18 17:45:12 -04:00
tests Wait till all log files are in ElasticSearch 2013-09-18 13:55:37 -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 Make bot.py behave like a daemon 2013-09-18 17:45:12 -04:00
elasticRecheck.conf Make bot.py behave like a daemon 2013-09-18 17:45:12 -04:00
elasticRecheck.py Make bot.py behave like a daemon 2013-09-18 17:45:12 -04:00
proof_of_concept.py Add reqs file 2013-09-12 17:01:32 -07:00
queries.json add query for bug 1226791 2013-09-17 13:00:20 -07:00
recheckwatchbot.yaml Make bot.py behave like a daemon 2013-09-18 17:45:12 -04:00
requirements.txt Add irc bot support to elasticRecheck 2013-09-17 00:27:14 -04:00
tox.ini Add tox.ini file for flake8 ignores 2013-09-18 13:47:18 -07: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