English
| Showing entries 1 to 20 |
A new release for mycheckpoint: lightweight, SQL oriented MySQL monitoring solution.
If you're unfamiliar with mycheckpoint, well, the one minute sales pitch is: it's a free and open source monitoring tool for MySQL, which is extremely easy to install and execute, and which includes custom queries, alerts (via emails), and out of the box HTTP server and
[Read more...]I've followed with interest on Baron's Why don’t our new Nagios plugins use caching? and Sheeri's Caching for Monitoring: Timing is Everything. I wish to present my take on this, from mycheckpoint's point of view.
So mycheckpoint works in a completely different way. On one hand, it doesn't bother with caching. On the other hand, it doesn't bother with re-reads of data.
There are no staleness issues, the data is consistent as it can get (you can never get a completely atomic read of everything in MySQL), and you can issue as many calculations as you want at the price of one take of monitoring. As in
[Read more...]Documentation is an important part of any project. On the projects I maintain I put a lot of effort on documentation, and, frankly, the majority of time spent on my projects is on documentation.
The matter of keeping the documentation faithful is a topic of interest. I'd like to outline a few documentation bundling possibilities, and the present the coming new documentation method for common_schema. I'll talk about any bundling that is NOT man pages.
This is the initial method of documentation I used for openark kit and mycheckpoint. It's still valid for mycheckpoint. Documentation is web-based. You need Internet access to read it. It's in HTML
[Read more...]
First of all, I wish you a happy new year.
Many things happened last year, it was really exciting to be involved in the MySQL ecosystem.
I hope this enthusiasm will be increased this year, up to you !
To start the year, I propose the MySQL[plus] Awards 2011
It will only take 5 minutes to fill out these polls.
Answer with your heart first and then with your experience with some of these tools or services.
Polls will be closed January 31, so, vote now !
For “other” answers, please, let me a comment with details.
Don’t hesitate to submit proposal for tools or services in the comments.
[Read more...]This post continues Generating Google line charts with SQL, part I, in pursue of generating time series based image charts.
We ended last post with the following chart:
[Read more...]
In this series of posts I wish to show how Google Charts can be generated via SQL. We discuss the Google Charts limitations which must be challenged, and work towards a simple chart.
I’m going to present the algorithm I use in mycheckpoint, a MySQL monitoring utility, which generates Google charts by raw data using views. An example of such chart follows:
[Read more...]
Revision 208 of mycheckpoint, a MySQL monitoring solution, has been released. New and updated in this revision:
MySQL@Facebook team have recently published an Online Schema Change code for non blocking ALTER TABLE operations. Thumbs Up!
The code is derived from oak-online-alter-table, part of openark-kit, a toolkit I’m authoring. Looking at the documentation I can see many ideas were incorporated as well. And of course many things are different, a lot of work has been put to it by MySQL@Facebook.
openark-kit is currently released under the new BSD license, and, as far as I can tell (I’m not a lawyer), Facebook’s work has followed the license to the letter. It is a strange thing to see your code incorporated into another project. While I knew work has begun on the tool by
[Read more...]Revision 190 of mycheckpoint, a MySQL monitoring solution, has been released. New and updated in this revision:
Revision 170 of mycheckpoint, a MySQL monitoring solution, has been released. New and updated in this revision:
Revision 132 of mycheckpoint has been released. New and updated in this revision:
Custom monitoring allows the user to supply with a query, the results of which will be monitored.
That is, mycheckpoint monitors the status variables, replication status, OS metrics. But it cannot by itself monitor one’s application. Which is why a user may supply with such query as:
SELECT COUNT(*) FROM shopping_cart WHERE is_pending=1
Such a query will tell an online store how many
[Read more...]Revision 118 of mycheckpoint has been released. New and updated in this revision:
With this new revision mycheckpoint turns into a monitoring solution for MySQL. One can now:
mycheckpoint is SQL oriented. As such, it allows for
[Read more...]Working on mycheckpoint, I have the intention of adding custom monitoring. That is, letting the user define things to monitor. I have my own thoughts, I would be grateful to get more input!
Monitoring for the number of SELECT statements per second, InnoDB locks, slave replication lag etc. is very important, and monitoring utilities provide with this information. But what does that tell the end user? Not much.
The experienced DBA may gain a lot. The user would be more interested in completely other kind of information. In between, some information is relevant to both.
Say we were managing an on-line store. We want to monitor the health of the database. But the health of the database is inseparable from the health of the application. I mean, having little to no disk usage is fine,
[Read more...]I’m having my usual fun with charts. Working on mycheckpoint, I’ve generated monitoring charts using the Google Chars API. But I’ve also had chance to experiment and deploy interactive charts, JavaScript based. In particular, I used and tweaked dygraphs.
I’d like to note some differences in using charts of both kinds. And I think it makes a very big difference.
I’ll call any image-based chart by “static chart”. It’s just a static image. Example of such charts are those generated by Google Image Charts (they now also have new, interactive charts), or RRDtool. Show below is
[Read more...]Revision #88 of mycheckpoint is released. In this revision:
mycheckpoint now monitors (on Linux only) three mount points:
It may well be the case that two of the above (or perhaps all three of them) share the same mount point. For example, if there isn’t any particular partition for “/tmp“, it is possible that the tmpdir (by default
[Read more...]Revision 76 of mycheckpoint comes with quite a few improvements, including:
When monitoring the local machine, mycheckpoint now monitors CPU utilization, load average, memory and swap space.
This only applies to the Linux operating system; there is currently no plan to work this out for other operating systems.
Examples:
[Read more...]mysql> SELECT os_cpu_utilization_percent FROM sv_report_chart_sample;
Rev. 57 of mycheckpoint has been released and is available for download.
New and updated in this revision:
It is now possible to monitor one host, while writing into another. Either or both could be remote hosts:
[Read more...]mycheckpoint
-0
I’ve hit a recent change which took me by surprise.
I was used to checking for the ‘questions‘ global status variables to see the total amount of queries the server performs. So, for example, I could run com_select/questions to learn the SELECT ratio out of all queries.
Apparently, as of 5.0.72-5.0.76 & 5.1.31 this has changed. A new status variable was introduced, called ‘queries‘.
The change being? questions does not any longer indicate the number of queries the server has executed: only the number of queries requested by the client (so, calling on a stored routine only counts as 1, regardless of how many queries the routine executes). The new queries variable indicates
[Read more...]mycheckpoint (see announcement) allows for both graph presentation and quick SQL access to monitored & analyzed data. I’d like to show the power of combining them both.
Taking a look at one of the most important InnoDB metrics: the read hit ratio (we could get the same graph by looking at the HTML report):
[Read more...]SELECT innodb_read_hit_percent FROM sv_report_chart_sample \G *************************** 1. row *************************** innodb_read_hit_percent:
I’m proud to announce mycheckpoint, a monitoring utility for MySQL, with strong emphasis on user accessibility to monitored data.
mycheckpoint is a different kind of monitoring tool. It leaves the power in the user’s hand. It’s power is not with script-based calculations of recorded data. It’s with the creation of a view hierarchy, which allows the user to access computed metrics directly.
mycheckpoint is needed first, to deploy a monitoring schema. It may be needed next, so as to INSERT recorded data (GLOBAL STATUS, GLOBAL VARIABLES, MASTER STATUS, SLAVE STATUS) — but this is just a simple INSERT; anyone can do that, even another monitoring tool.
It is then that you do not need it anymore: everything is laid at
[Read more...]| Showing entries 1 to 20 |
