Auto-tools/Projects/OrangeFactor: Difference between revisions

Jump to navigation Jump to search
(add a link about fixes)
Line 41: Line 41:
== Architecture ==
== Architecture ==


The system will have several moving parts:
The system has several moving parts:


* a [http://hive.apache.org/ Hive] database ({{bug|601028}}), hosted by the metrics team, which will store raw logs, and an [http://www.elasticsearch.com ElasticSearch] database, which will store data parsed out from the buildbot logs
* modifications to TBPL that write orange comments to a database


* a [http://flume.csail.mit.edu/doku.php?id=flume flume] agent, which will move logs from the into the Hive and ElasticSearch databases hosted by metrics
* a [http://pulse.mozilla.org/ Mozilla Pulse] consumer that listens for buildbot messages that are generated when unit tests are finished


* a unittest [http://hg.mozilla.org/automation/logparser/ logparser] ({{bug|601216}}), that will parse buildbot test logs and produce output that gets fed into the ElasticSearch db via flume
* a unittest [http://hg.mozilla.org/automation/logparser/ logparser], that parses buildbot logs, and feeds the resulting data into ElasticSearch


* a web dashboard that pulls data from the database and displays various interesting statistics about it
* an instance of [http://www.elasticsearch.org/ ElasticSearch], which is hosted by the Metrics team, that stores the parsed log data and the TBPL bug data
 
* a [http://brasstacks.mozilla.com/orangefactor/ web dashboard] that pulls data from the database and displays various interesting statistics about it


== Making Oranges Interesting ==
== Making Oranges Interesting ==
Confirmed users
1,905

edits

Navigation menu