At CALUMO, we love to make sure that our system is running fast and is stable. Our clients move to CALUMO-as-a-Service because their existing reporting, BI and budgeting systems are slow. Their BI systems are either really old, expensive to "upgrade" or they are very manual like using Excel for budgeting and reporting. So the only way to ensure we keep CALUMO-as-a-Service in tip top condition is to constantly measure the our systems. The detailed analytics of the CALUMO software usage and performance is all logged on a central logging server, within the CALUMO product. All these calls are made asynchronously so as not to impact performance.
CALUMO analytics contains:
CALUMO analytics does not:
There are several reasons we send a summary set of user information, the first is so that we can match up the automated errors logged with support issues that are being sent in via firstname.lastname@example.org. This is invaluable for us in support because we have a way to see what errors are occurring for a given user not just at the current point in time, but also over time. It also allows us to see these errors without having to log into the customers server and have the user replicate their action.
Secondly, we are building a program where we can look at the feature usage of a given user over time and have notification show to the user about:
The main focus of this feature is all about guided user training, getting our users up to speed on what they are doing now and what, logically, they would be doing next as a way of reducing the need for our customers to spend on training.
Another reason is that we want to use it is to give the owners, key stakeholders of CALUMO at our customers, through our customer portal, statistics on their users usage of the product over time with metrics like:
If you have any other ideas you'd like to share on this, please let us know!