(→Comparison of candidate ETL/reporting) |
(Add Drupal) |
||
| Line 71: | Line 71: | ||
{| | {| | ||
! !! ETL import !! Pentaho reports !! Jaspersoft reports | ! !! ETL import !! Pentaho reports !! Jaspersoft reports | ||
| + | |- | ||
| + | | Drupal || MySQL import || || [http://drupal.org/project/query_export Query Export for Jasper] | ||
|- | |- | ||
| Bugzilla || MySQL import || [http://sourceforge.net/projects/qareports/ Bugzilla analytics] || [http://jasperforge.org/projects/bugzillareportswitholap Bugzilla reports with OLAP] | | Bugzilla || MySQL import || [http://sourceforge.net/projects/qareports/ Bugzilla analytics] || [http://jasperforge.org/projects/bugzillareportswitholap Bugzilla reports with OLAP] | ||
The goal is to provide a web page summarising metrics about various aspects of the MeeGo project. The data should update regularly - depending on the metric, that could be real time or updated automatically on a regular basis.
The dashboard will track the following community resources, ideally:
The data should also be available for custom reports for usage and analysis in the monthly MeeGo Metrics report published by User:DawnFoster
To fulfill these goals, the dashboard will gather data from the various resource into a centralised database, using some sort of Business Intelligence platform including ETL for data acquisition and storage, and a reporting service for generating reports and dashboards.. A web page will provide a view into this database with predefined reports.
Candidate reporting solutions:
The following are essentially ETL engines, and do not provide reporting or dashboard functionality:
MuleSoft is an open source ESB, but does not seem adapted to our needs. The field is thus narrowed to Pentaho and JasperReports.
For each community resource, we need to figure out how to get the data into a usable form, and come up with appropriate queries for metrics reports, and finally present the results on a webpage.
The area of Business Intelligence is littered with acronyms. Here's a quick overview of the main ones, and how they all fit together.
So, in short, the community dashboard project will likely use an ETL to plug data into an OLAP server, and then use a business reporting engine to query that data and present it in a dashboard.
Modules available:
| Software | License | ETL | OLAP database | BI server | Reporting | Dashboard module |
|---|---|---|---|---|---|---|
| Pentaho | EPL | Kettle | Mondrian | Pentaho BI Platform | Pentaho Reporting | Community Dashboard Framework |
| Jaspersoft | AGPL v3 | JasperETL (Talend Open Studio) | JasperOLAP | JasperReports Server | iReports editor | No (commercial only) |
Support for community applications:
| ETL import | Pentaho reports | Jaspersoft reports | |
|---|---|---|---|
| Drupal | MySQL import | Query Export for Jasper | |
| Bugzilla | MySQL import | Bugzilla analytics | Bugzilla reports with OLAP |
| MediaWiki | MySQL import | ||
| Transifex | ? | ||
| Mailman | MySQL import via mlstats | ||
| IRC | ? | ||
| Forum | ? | ||
| Web analytics | ? | ||
| git | Via gitdm? |