As for the comment above, I do not feel that the mycheckpoint’s current measurements inflicts too much load on the server for me to worry about.

There may be a case that you need to install it for each database server, but hey.. its free… and you can just have one main server query the tables on each server’s mycheckpoint tables.

2) Yes. I have first encountered it slightly more than 3 years ago on a customer’s site, and it made a good impression.

1)
“Why do you say python is non-cross platform though?”. I was referring Windows where Python is not ‘native’. It may be installed of course. But most Windows users are unfamiliar with handling such Unix-style environments.

2)
MONyog has been available to the public for 4+ years now.

1) mycheckpoint does not have to touch the servers it monitors. It need to write the data somewhere, and that can be a small MySQL server dedicated for storing monitored results. I *can* use the same servers being monitored.

mycheckpoint can run on the same machine as monitored MySQL server, or from a remote machine. The advantage of running it on same machine as server is then the ability to monitor OS data (disk IO, disk usage, load average, etc., all very basic). Or you can monitor remotely and skip OS monitoring.

It’s definitely possible to have one mycheckpoint instance to maintain. If you want it to monitor 200 servers, just execute it 200 times with different “–monitored-host” and “–database”.
It does require a different schema for each monitored server.
See here.

I cannot at this time have a unified page of multiple servers on one page. It’s a pending request, and I haven’t got round to that.

2) mycheckpoint uses SimpleHTTPServer class from python. It’s pre-built in any python distribution, to the best of my knowledge.
Why do you say python is non-cross platform though?

I do wish to make the point that mycheckpoint indeed is not tested on MS Windows; I have no knowledge about anyone using it on Windows.

So I would say mycheckpoint is 98% self-contained: it requires python (available on all unix machines), python-mysql (needs to be installed by user), and, like MONyog, external mail service.

3) Same. See here: installation instructions for required GRANTs.

So, for these three concepts, I don’t see that great a difference.

—
Like I said, there’s no comparison about the scope of the two. I’ve worked alone on mycheckpoint for about a year on my spare time. I have no idea about the team size for MONyog; obviously a *whole lot* time has been invested.

I’m not saying mycheckpoint is *as* feature rich as MONyog. It is not. MONyog has a richer feature set.

I’m saying that saying “like never before” on custom queries is something that makes me want to write a blog post such as this one.
“Like never before” is a marketing phrase, and that’s fine; but I wish to point out there are plenty installations on mycheckpoint (I don’t know how many, I’m judging by downloads only) for whom “like never before” does not fit.

The main difference between concepts (not discussing features) are, I think

1) MONyog does not at all touch the server(s) monitored. Nothing stored here. Also nothing executable to run on the servers monitored. MONyog is ‘agentless’. I don’t know if you can monitor 200 MySQL servers and have only one mycheckpoint instance to maintain? Can you (more or less easily) have a unified view of multiple MySQL servers in one page?

2) MONyog has built in its own HTTP daemon, its own database and its own script-intepreter (javascript) and does not depend on availability of a (non-cross platform) runtime (Perl, Python, .NET, whatever) on the system(s) where MySQL is running and/or MONyog is installed. MONyog is 100% ‘self-contained’ (with the sole exception that an external service is required or mail- or trap-alerts)

3) MONyog needs very few privileges to MySQL and to the systems where MySQL(s) is/are running – because you don’t need to install and configure anything there.

Am I missing something?