Dear MoSKito-rians and those to become MoSKitorians in the next year!
This year was very successful for MoSKito: about 15 releases, multiple conference and press appearances, and a lot of user activity, especially by the end of the year. All of this makes us really proud of our project.
Looking back at our achievements, we are holding still for a moment to enjoy the Quietness of the next two weeks before the next year, which promises to be even more inspiring and exciting.
We would like to use this moment and wish you quiet, recreative and contemplative holidays and a very successful 2014.
Leon Rosenberg and the MoSKito Team.
MoSKito enables you to analyze and monitor your running Java application.
During this blog post, we guide you how to fully integrate MoSKito within Java EE 6 environment und run it with JBoss Application Server 7. Furthermore we provide some hooks for integrating Producers, Threshold and Accumulators.
In previous steps, we spoke about general integration of MoSKito and WebUI and adding custom counters. Today, we are going to dive deeper and build own stats object.
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.