Stats Collector

Simple configurable web application to collect and display statistics from various sources (currently Gerrit, in the future Sonar and Jenkins)

Designed to be displayed on a TV or other visual device to allow software teams to view statistics.

Build Status

Usage

• Copy the contents of the "dist" folder to a directory on the machine you wish to run the application on.
• Alter the .sh or .bat script to specify the port you wish the web interface to run on.
• Set your initial parameters in the GerritStatistics.properties file.
• Run .bat or .sh file as appropriate.
• Open up https://localhost:YOUR-PORT (default is 8080)
• Go to the config tab at the top and entry your Gerrit server details (See below for help setting the thread limits)
• Go to the config tab at the top and entry your Sonar server details
• Setup on a browser to show the data ! (currently manual refresh is required)
• You can override the default Project Name and Project Regex config items (i.e. if you have multiple projects ont he same gerrit server and want the stats to be seperated) by using the following URL example: https://StatsCollector/home?projectName=TestProj&projectRegex=.*testproj.*&sonarProjectRegex=.*testProj.*

To Change The Default Port

• Open the .bat or .sh file and update the port in there.

To Create Your Own SSL Key

• Generate a self signed p12 file (or use a real one)
• Place it in the same folder as the jar file (replacing keystore.p12)
• Update the keystore password in application.properties to match the one for your file

Third Party Libraries

Stats Collector uses the following projects:

JS

• Twitter Bootstrap
• AngularJS
• UIBootstrap
• ChartJS
• tc-angular-chartjs
• FileSaver.js
• ng-file-upload
• formly

Java

• SpringBoot
• google-gson
• google-guava
• log4j
• Joda Time
• Apache Commons Configuration
• Apache Commons IO
• Apache Commons Beans Utils
• JUnit
• Mockito
• Powermock
• JSTL
• Jackson JSON Schema Module

Setting Thread Limits

The thread limit setting in the Gerrit config decides how many items each thread can process when pulling back details from Gerrit. For example if you have 6000 changes in gerrit and have the thread limit set to 2000 (default) the app will run up 3 threads to process the information each time it is cached. As each of these threads creates a HTTP connection to your Gerrit box every 15 minutes if you have the limit set low (as in the example above setting it to 200 would result in 30 threads) then you can overwhelm the gerrit server resulting in missing stats as the connections fail. Ensure you check the logs to see if any errors occur the first time you collect stats, any errors should be reported back to the UI in the connection status alert.