https://forge-allura.apache.org/p/allura/tickets/You searched for labels:"metrics"enThu, 20 Aug 2015 22:07:56 -0000https://forge-allura.apache.org/p/allura/tickets/5518/In Bitergia we have developed an Allura module to show different metrics about software projects. As examples commits in git, opened/closed/changed tickets in Allura tickets or emails sent in mailing lists. We use our VizGrimoire library to do the data analysis and visualizations using the data gathered from MetricsGrimoire. An example of [Allura project](http://blog.bitergia.com/2012/11/13/some-charts-about-allura) A branch will be created in Allura git to integrate the last VizGrimoire with an Apache license and the key visualizations will be implemented for Allura projects.Alvaro del CastilloSun, 18 Jan 2015 21:55:05 -0000https://forge-allura.apache.org/p/allura/tickets/5518/https://forge-allura.apache.org/p/allura/tickets/3435/Determine and run some queries to check the monq_task collection to find causes for slowness. Document the queries here in this ticket for future reference to run again if needed. Here are a few: ** in progress, and pending** db.monq_task.find({state:'busy'}).count() db.monq_task.find({state:'ready'}).count() **raw quantity per day** db.monq_task.find({time_queue: {$gt: ISODate("2011-12-13T00:00:00.000Z"), $lt: ISODate("2011-12-14T00:00:00.000Z")}}).count() ** recent tasks that took over 5 minutes ** db.monq_task.find({'$where': "this.time_stop.getTime() - this.time_start.getTime() > 5*60*1000", time_stop: {'$ne': null}, time_start: {'$gt': ISODate("2011-12-10T00:00:00.000Z")}}).count() ** what is assigned to each process ** db.monq_task.find({'state':'busy', time_start: {$gt: new Date(Date.now() - 1000*60*60*48)}}, {process:1,task_name:1,time_start:1}).sort({'process':1}) ** details of current process ** db.monq_task.find({'state':'busy', time_start: {$gt: new Date(Date.now() - 1000*60*60*3)}}) ** check an individual process activity ** > sudo -u allura strace -p 6406 > kill -USR1 -p 6406 # need siteops to run; will print current task to /var/log/allura/allura.log ** types of pending tasks ** db.monq_task.distinct('task_name', {'state':'ready'}) q = {'state':'ready'} db.monq_task.distinct('task_name', q).forEach(function(t){ print(t, db.monq_task.find({$and: [q, {task_name:t}]}).count()) })Dave BrondsemaMon, 23 Feb 2015 09:33:27 -0000https://forge-allura.apache.org/p/allura/tickets/3435/https://forge-allura.apache.org/p/allura/tickets/2084/In allura, invoke the methods exposed by [#2083] and put a nice UI on it to serve up the reports to admins. UI is TBD, many JS libraries are good options. Download stats use jquery.flot.js which is decent.Dave BrondsemaSun, 29 Mar 2015 04:29:02 -0000https://forge-allura.apache.org/p/allura/tickets/2084/https://forge-allura.apache.org/p/allura/tickets/2083/Alongside the aggregator [#2082], provide a service to expose the aggregated results. Should take a few parameters like report name, start/end timestamp, granularity (day). The simplest possible for right now would be just a python function (as opposed to a json webservice). In [#2084] allura can import this module and invoke it directly.Dave BrondsemaFri, 20 Mar 2015 23:24:55 -0000https://forge-allura.apache.org/p/allura/tickets/2083/https://forge-allura.apache.org/p/allura/tickets/2082/A reporting service that reads report definitions and aggregates results daily from the event stream. Weekly & monthly aggregates would be very good also. This should be a standalone package, but can be in the allura codebase. Ideally it would have *no* deps on Allura. Simplest possible implementation of reports would be python files that conform to some interface (e.g. have function 'report') See also http://groups.google.com/group/mongodb-user/browse_thread/thread/6ee72dff92e6ea93/d88d62ac1cd6565c for related discussion Also see [#2034] for required reports.Dave BrondsemaThu, 20 Aug 2015 22:07:56 -0000https://forge-allura.apache.org/p/allura/tickets/2082/https://forge-allura.apache.org/p/allura/tickets/2078/A collection of documents with fields: timestamp, event type (string), user, project, neighborhood, app, request dict. I think strings would be better than objectid references for user, project, neighborhood, and app. That'll make insertion from non-allura sources easier, and reporting too. Dave BrondsemaThu, 20 Aug 2015 22:07:54 -0000https://forge-allura.apache.org/p/allura/tickets/2078/https://forge-allura.apache.org/p/allura/tickets/2035/Graph showing the how many users have been "active" in the past 30, 90 and 180 days. Active == done anything (scm commit, file release, metadata update, forum post, wiki edit, etc) except consumer activities (e.g. post a review). Check with Mark, but I think it'd make sense to do Classic & Beta separately.Dave BrondsemaTue, 31 Mar 2015 16:09:40 -0000https://forge-allura.apache.org/p/allura/tickets/2035/