The Kadira client looks like it works great for collecting performance data from the Meteor applications.
However, once we get to the Kadira server, things get complicated. It was designed to be a SaaS product, and as a result, it has many features not related to performance management, it relies on many services, it has to support a lot of requests, and so on. Plus, it would be natural to think there are some issues and/or bugs present.
I’m wondering, why not repurpose Kadira Client to store all the data it collects into the application database (or a secondary database) and then build a simple interface to view all of it? Perhaps we can even cut out some non-key features to keep things really simple.
I would be happy to start some kind of group and build the interface part to run with-in a user’s app.