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.
Slowly but inevitable the holidays are coming and with that an urge to make some kind of retrospective for 2013. We will not do that. But instead we will shortly speak about recent MoSKito development and what lies ahead in 2014.
Why do you need software architecture?
Lately, some of our colleagues had a hard time working with MoSKito documentation. Docs are fine, they said, but finding things is difficult. Sadly, that was true. Why?
MoSKito is quite a mature project. It has been developing for the last 6 years, which is a long time for our quickly changing Internet era.
Many MoSKito contributors added new features, but didn’t have time to fix the old documentation. What they did was writing new docs on top of the ones we had. As a result, MoSKito Confluence Space was full of valuable info, which was totally in a mess.
Now, MoSKito documents are getting a new lease of life 🙂
What did we change? Continue reading
Since the beginning of our open source engagement (and my personal java life), we’ve been working with log4j. By that time, log4j was de-facto standard in the JAVA world. However, it’s time to say Goodbye to an old friend and move on to SLF4J.
Recently, you could say there were no serious movements in MoSKito Camp. But this was just a tactical trick, the calm before the storm.
Now we’re back with a bunch of updates! We shall describe them one by one, so that you could feel their true value. So, today’s special is…
Brand new moskito.org website!
Let’s take a look and say why is it great. Continue reading
MoSKito is a relatively old (and mature) project by Internet reasoning (it made its first appearance in 2007). The project has been evolving fast, which led to re-arrangements among its components and caused some chaos in naming.
The intention of this post is to explain who’s who in MoSKito Universe. Meet the Swarm!
Since 2.1.0 version, configureMe provides the ability to view a list of configuration files, each config file separately, and its attributes, that used by default environment and content of this configuration.
For this functionality was used JMX API, namely managed beans, or MBeans and created MBeanRegisterUtil class. This class contains regMBean method, which doing registration of your mBean in MBean server. And also had been created mBeans for providing information about your configurations files:
WatchedConfigFilesMBean – provides list of config files.