Apache and Nginx web servers both expose a very nice interface for polling the web server status via HTTP, providing you with useful counters for statistics and up-time.
Read the full post

Apache and Nginx web servers both expose a very nice interface for polling the web server status via HTTP, providing you with useful counters for statistics and up-time.
Read the full post
Incentive for raw commandsM3 (or its newer version which you should be using – M3v3) can do pretty much. However it can’t do anything.
M3 is good at timing execution of commands, apply simple parsing and upload the data to Monitis. Allowing you as the SysAdmin (and end-user of M3) to easily shape and design Custom Monitors for your system improving overall system uptime and stability.
Many times this is indeed what happens when trying to monitor different applications. The simple process of ‘Execution -> Parsing -> Reporting’ gets the job done. What happens when it doesn’t?
Well, I’ll tell you what happens – you are left a bit puzzled and think you’ll have to implement the Custom Monitors API which Monitis provide. True – until not long ago.
M3v3 bring you ‘Raw Commands’ capability in its last version.
Read the full post

ntop is a very simple yet powerful bandwidth monitor which outputs various statistics counters in RRD.
RRD – Round Robin Database – is a very handy framework for saving server performance counters in a ring buffer.
We can say that if we would like to graph network performance, ntop does most of the hard work for us and all we have left to do is to graph the counters.
Among the counters ntop exposes there are:
And speaking of graphing, we have Monitis, which can graph any counter we can think of. I have an idea – lets graph ntop data with Monitis!
Read the full post

Had I been told to monitor a cat chasing a mouse with Monitis, my answer would have been – “Yes, it’s probably possible”.
With the not-so-recent addition of M3 to the arsenal of monitoring tools Monitis can utilize, it is possible to monitor anything. However this alone is far from being enough. Smart implementations of proper applicative monitoring is what should be practiced.
Read the full post

During the lifespan of M3 (Monitis Monitor Manager) there has always been something lacking – timers.
M3 execution procedure was outlined in this previous article.
The execution mentioned in the latter was a one-time-execution, whereas server monitoring requires periodic invocation of monitors in order to actually provide counters over time, graphing performance.
The periodic invocation method suggested up until today was to integrate M3 with crontab.
Crontab, in a nutshell, is a Linux/Unix service for periodic invocation of executables. Implementing M3 with crontab properly meant M3 would run every X minutes, producing a Monitis counter update every X minutes, should everything run properly.
In the following article I’ll outline the changes done to support timers in M3.
Read the full post
Monitis GFI is a specialist provider of web and Cloud monitoring services that include website monitoring, site load testing, transaction monitoring, application and database monitoring, Cloud resource monitoring, and server and internal network monitoring within one easy-to-use dashboard. Over 100,000 users worldwide have chosen Monitis as their provider of choice to increase uptime and user experience of their services and products. What makes Monitis' solutions different is that they are fast to deploy, feature-rich in technology and provide a comprehensive single-pane view of on-premise and off-premise infrastructure and applications.