Now it’s time to setup proper monitoring to avoid unpleasant surprises in future.

There are two major problems the monitoring solves: alerting and trending. Alerting is to notify a responsible person about some major event like service stopped working. Trending is to track the change of something over time – disk or memory usage over time, replication lag etc.

This post will be about alerting with Nagios.

The major problem with most of Nagios setups I’ve seen is excessive amount of false positives. This kills whole idea of monitoring. The matter is when an admin gets a false alert they tend to mute it, explicitly or implicitly. They either filter alerts out or don’t treat them seriously. In general case the alert must be worth to wake up the admin in the middle of the night. If the alert isn’t worth as much the real problem will be ignored sooner or …

Here at Monitis, we’re on a mission to not only build the best product but also, at the same time, make it more user-friendly. We listen to your feedback and suggestions and take various steps to improve our services, tools and features to make YOUR life easier. In any given week, you can see a new feature or update in your Monitis dashboard. Here’s some of the stuff we’ve added since our last newsletter, three months ago. Stay-up-to-date and see all that we have to offer by reading about all our changes below:

(more…)

I’m pleased to announce that my first book, the InnoDB Quick Reference Guide, is now available from Packt Publishing and you can download it by clicking here. It covers the most common topics of InnoDB usage in the enterprise, including: general overview of its use and benefits, detailed explanation of seventeen static variables and seven dynamic variables, load testing methodology, maintenance and monitoring, as well as troubleshooting and useful analytics for the engine. The current version of MySQL ships with InnoDB as the default table engine, so whether you program your MySQL enabled applications with PHP, Python, Perl or otherwise, you’ll likely benefit from this concise but comprehensive reference guide for InnoDB databases.

Here are the chapter overviews …

As a follow up to the previous post about logstash, here are a couple of related init scripts for anyone implementing the OpenSource Log Analytics setup that is explained over at divisionbyzero. These have been tested on CentOS 6.3 and are based on generic RC functions from Redhat so they will work with Redhat, CentOS, Fedora, Scientific Linux, etc.

• Init script for ElasticSearch: located in the repo by clicking here – servicewrapper required
• Init script for Kibana: …

We’ve all heard the term “Big Data” thrown around a fair amount in the last several years ever since the rise of Hadoop and other distributed storage methods. But defining “Big Data” has always been a subjective term that hinges on perspective; what one engineer considers big can be vastly different than another’s.

However, there’s finally a definite description that says Big Data no matter what perspective you operate from: “That facility by my calculations that I submitted to the court for the Electronic Frontiers Foundation against NSA would hold on the order of 5 zettabytes of data. Just that current storage capacity is being advertised on the web that you can buy. And that’s not talking about what they have in the near future.” You can read more about the facility and its purpose here: …

MySQL performance can be increased in two ways, software optimization and hardware upgrades. While the previous articles have covered much of the software side of performance optimization, we are now going to focus on the hardware aspect. Does hardware help boost performance? Like software optimization, hardware upgrades for MySQL systems are based upon set goals for an organisation. The question is not what hardware would work best; rather a question of what hardware will help the organisation achieve an X goal. The answer is yes, hardware does boost performance, but there are a few caveats to this. There are cases such as organizations’ demands are fulfilled even with crappy hardware, and all they require is a performance boost on the software side. However, an organisation might have a goal plan for a major performance increase down the road, and …

MySQL is the world’s most popular open-source database and platform for millions of web applications – it’s critical but cumbersome to monitor.

Monitis’ MySQL monitoring provides three key benefits:

Insight
» 246 potential monitoring variables
» 21 aggregated, percentage-based metrics
» Adjustable thresholds to separate real issues from false alarms

Control

» Monitor entire IT universe from one dashboard
» Quick diagnosis & root cause detection

Simplicity
» Cloud-based means no need to install, update or maintain it
» Leaves you time to focus on more important things

For a FREE trial, go to:

…

New feature provides significantly faster insight and root cause analysis

SAN JOSE, Calif., February, 15, 2012 – Monitis, the leading cloud and web application monitoring software provider, today announces that it has added comprehensive MySQL database monitoring to its award-winning Application Performance Management & Monitoring platform. The robust Software-as-a-Service (SaaS) tool enables users to gain significantly faster insight when conducting root cause analysis.

The MySQL monitoring feature includes 246 monitoring variables and more than 21 different metrics to provide one of the easiest to use, yet comprehensive database monitoring tools available. It was first introduced into the free Monitor.Us platform back in June last year and has seen the code battle hardened by many hundred free users over the last 8 months.

…

Pluggable M3 (Monitis Monitor Manager) Framework

Who needs an introduction about M3? – Perhaps no one!
After gaining some reputation with M3, providing extra-easy integration of any monitor into Monitis it was time to take it to the next level.

Generally speaking, the work flow of M3 was described in detail in this article.

After some thought and design, we’ve decided it’d be best if M3 was pluggable. Pluggable in terms of being able to easily add execution and parsing plugins.
The interface and behavior of M3 …

The MySQL database is a crucial part of a wide variety of products, particularly web applications. Naturally, it is very important to monitor the health status of MySQL.  However, there is constant disagreement on which of the many MySQL status variables provide the best overview on MySQL health status and indicate that something is not right with a server.

It certainly depends on what your application does – tuning read performance is different than optimizing write operations and everything changes when you have a cluster. The average user can use small subset of variables while advanced user want to get more detailed picture of the situation. So there cannot be one set of “magic variables” to quietly optimize every situation. However, it is possible to have a more-or-less optimal set of metrics that will allow to get a “good enough” notion about the general health status of MySQL Server.

The new white paper “ …