The Internet is a great resource, but it is sometimes too much to wade through hundreds of web pages looking for tips about using Tomcat with a database. So we at Monitis have done it for you! Below are some of the more useful tips found in various places on the Internet.

Monitis’s existing Java SDK provides you with almost all possible ways to create any internal monitoring agent that a user wants. But, unfortunately, Java gives you no simple way to build a custom monitor. Adding a couple of simple classes into the existing API opens the simplest way to build, in fact, almost any type of custom monitor. Below we describe the additions to the existing API that allow you to do so, and we’re also providing a corresponding example.

Let’s face it; the Internet world today lives by Java. But not everything associated with Java runs smooth.

For example, many Java applications create log files by using a famous Log4J mechanism. Often, these applications are located remotely, and there is no actual way possible in real time to monitor the logs alerts. That often means that it’s difficult or impossible to avoid some dangerous situations in time, including stopping applications because of faults.

This article is presenting one of the possible ways to build a Monitis Custom monitor that can provide real-time monitoring for Java applications logs.

The existing Monitis Java SDK (that uses the Monitis Open API functionality) provides almost every opportunity to create any internal monitoring agent that a user could want. It is really very easy to build a monitor by using Monitis Open API and Monitis Java SDK. 

Below we’ll describe possible ways to build a custom monitor for monitoring Memcached server health in real-time – based on improved Monitis Java SDK.