Today we are going to connect MoSKito-Central to MongoDB database.
In a few words, MoSKito-Central is a service (remote or embedded) that receives your MoSKito statistics and stores it in the place of your choice (Filesystem, Database, …).
Our choice for now is MongoDB and MoSKito-Central in embedded mode.
In all previous steps, we integrated MoSKito into our application and set up data storage. In simple words, we learned how to monitor our app’s performance and store the obtained MoSKito data for later analysis. What’s next?
Here’s the good news: our burgershop is now the world’s leading burger-seller, with million revenues. It has become a big distributed app, with multiple instances and servers.
The bad news: even the smallest fail might lead to a thousand-euro loss per minute.
The question: how to keep trace of hundreds of producers on a dozen of instances? It’s the moment to call
Superman another hero!
So, today we’re setting up MoSKito-Control, a tool for monitoring multi-node web applications.
In previous post, we performed general integration of MoSKito into the target project.
In today’s step (rather short), we’re going to add some business-value-related information with a Counter.
After we created our guinea pig in the previous step, it’s now time to integrate MoSKito-Essential into our application. Our plan for today is:
- Add monitoring to the core parts of our code.
- Download and connect MoSKito Inspect
- Learn about WebFilters and Listeners
At the end of the guide we want to:
- see the access data in MoSKito Inspect,
- record a Journey.
Despite the efforts we put into MoSKito documentation, we are continuously facing questions like ‘How to do this’ and ‘How to get that’.
Now we want to give you a guide for the whole setup cycle, which this posts starts.
The guide will cover a complete application lifecycle with MoSKito, from integration of the first MoSKito-Essential Producer to installing MoSKito-Control and MoSKito-Central setup.
But before we start, we need a guinea pig. This is what we do today – set up a simple application for experimental purposes.