Kill’em all

People have been asking us time over time, if it’s possible to disable MoSKito in a running system completely. Also we don’t understand why you’d ever want to do it, after first pull request for this feature has been opened, we understood that people are quite serious about it. Well your wish, is our command, so here it goes.

Continue reading

New built-in tags

We continuously monitor how other developers use MoSKito with a wide variety of their web-apps, we carefully listen to their feedback and in response we keep adding new features along with tweaking existing ones to make MoSKito more and more robust with every released version.

 

Today we would like to introduce you two more built-in tags. These new tags were found to be highly useful in real working environments. They will save you a lot of time and they will allow you to understand reasons behind certain bugs much easier.

Continue reading

Better MoSKito Dashboard with Chart and Producer Patterns

Custom dashboards are clearly one of the most useful visualization features MoSKito has to offer. The ability to see all related information at a glance collected in one place improves the analytic capabilities and help tracking the anomalies. However, until now, configuring a dashboard could be cumbersome especially with high amount of charts and producers. Also adding a new producer to the system would require to add it to the dashboard explicitly, a step that could easily be overlooked. With MoSKito 2.8.7 we improved!

Continue reading

Distributed subject observer pattern with ano-plass and DistributeMe

Asynchronous notification aka publisher/subscriber model is a powerful pattern. Both ano-plass and DistributeMe offered a way to do it, one with subject/observer pattern, the other with the classical EventChannels. The ano-plass subject/observer pattern was limited to the current vm. Now it can become global.

Continue reading

Recipe: Monitoring a simple process with counters

From time to time we are asked by the users of MoSKito, how to do this or that, and how to implement a specific use-case with MoSKito. This is why we started a recipes section in our documentation and now also on the blog. A recipe will describe how to achieve a specific goal.

So the original question which led to this recipe: “Lets say I have a process, some kind of job, which is running every x seconds, and I want to monitor the number of successful and unsuccessful executions, with least possible effort”. And here how it goes.

Continue reading

Using Tags to catch unexpected bugs

MoSKito has many powerful features, it can monitor almost every aspect of your application, it is the worlds best open-source APM for Java. But sometimes all this functionality can be a bit overwhelming to the user, and you might run into some issues figuring out how monitor your app efficiently. To address this, and give you an example of problem solving with MoSKito, today we will give you an insight on a real life case of tracing bugs and optimizing your application using MoSKito.

 

Continue reading

Monitoring existing application using MoSKito Javaagent

In this tutorial we will demonstrate how to use MoSKito Javaagent to monitor existing web-application with no changes to the app’s source code. We will show how to add MoSKito Javaagent to the app deployed in Tomcat servlet container, and how to connect to this app using MoSKito Inspect.

Continue reading

How to control your loadbalancer

Applications grow. At least successful applications. At some point your growing application will require a loadbalancer. It may be for scaling or availability purpose or something else. The day your application runs behind the loadbalancer first time will make you proud. And it will make you ask, how can I control what the loadbalancer thinks of my application availability? This is how.

Continue reading