On Sat, May 21, 2016 at 1:31 AM, Ales Zelinka <azeli...@redhat.com> wrote: > d) Slightly related: with beaker-jobwatch I struggle to make people > investigate the cause of the aborts = if reschedule works they get their > results and no longer care that some other recipeset failed to finish. I > expect Beaker to have the same issue once it starts "fixing" jobs. Do you > have any ideas how to persuade people to investigate these? > > /me currently plans to add a phone-home feature to beaker-jobwatch that > would log all failed-to-finish recipesets into > logstash/ElasticSearch/Kibana, hoping that it will help me spot patterns of > failures and report better tickets.
I personally think it would be really cool if Beaker natively supported Elastic-recheck type functionality (given a suitable ELK installation to talk to): http://status.openstack.org/elastic-recheck/ However, the hard part of pursuing that idea wasn't reporting the results, it was getting access to an ELK installation that could plausibly handle the scale of Red Hat's main Beaker installation. Starting with just beaker-jobwatch managed jobs could help mitigate that by making it possible to calibrate the monitoring capacity needed to make it a standard feature. Cheers, Nick. -- Nick Coghlan Fedora Environments & Stacks Red Hat Developer Experience, Brisbane Software Development Workflow Designer & Process Architect _______________________________________________ Beaker-devel mailing list beaker-devel@lists.fedorahosted.org https://lists.fedorahosted.org/admin/lists/beaker-devel@lists.fedorahosted.org
