[Sayan Chaliha]

Yes, it has to do with the fact that you had 2.8.2 installed earlier. Even if you install both versions in different directories, it still uses the same directory for storing user data + the same registry keys. Mike, I'd suggest you create a ticket to continue this discussion because all forum posts are available for public viewing. We maintain complete privacy as far as our support system is concerned. You can create a support ticket here: http://www.webyog.com/support .

[Sayan Chaliha]

Hey Mike,

This forum is for queries pertaining to MONyog — MySQL Monitor. I'm sure you meant to post in one of the SQLyog forums… so let me just move the post for you, and I'm sure somebody will reply to your query at the earliest.

[Sayan Chaliha]

BTW, I should've asked this first: What does MONyog's log say?

[Sayan Chaliha]

Hey Mike,

I just double-checked the code… MONyog tries to open the file in read-only mode, that's for sure. It would help me a lot more if you could try and reproduce the case with the latest GA release of MONyog (ie, 3.76)… 2.8.2 is so old, and there have been so many changes since then including *several* major memory leak fixes. So I'd advise you to upgrade in any case. If that's not an option, then give me a couple of days and I'll set-up a similar environment as yours here and try and reproduce the case here, in our dev environment.

[Sayan Chaliha]

Hi Mike,

I'm under the impression that you're using SSH on Windows. Is that correct? There could be several reasons for this:

— If you're trying to access the log file through SFTP (ie, through the SSH server) be sure to select 'Via SFTP' in 'Log Settings' and not 'Local Path'.

— Ensure that the SSH user credentials that you're using has sufficient privileges to access the log file.

— If MONyog is running on a Windows system and the log file also is on a remote Windows system, I suggest you read FAQ #31 in MONyog's help doc (I'll paste the contents of the FAQ at the end).

To answer your question, MONyog opens the log file in read-only mode; never in write or read/write mode.

FAQ #31. MONyog cannot identify if destination of the log file is on a “Mapped Network Drive”. Why?

A: By default MONyog service runs under Local System Account. If you are having Slow query or General query log in a Mapped Network Drive, MONyog will not be able to reach it. If MONyog has to access the file present in a Mapped Network Drive, you have to convert the path into shared path (accessed with UNC notation: \systemshare) and then follow these steps:

• Click on Start menu, then click on run and then type,

services.msc

• After this 'Services' window pops up with list of all services running in your system.[*]Search for MONyog and then right click –> Properties.[*]Click on “Log On” tab and then you can see that MONyog is using “Local System Account”.[*]You need to use “This account” option and then give the credentials that you use to log on to the system with “Administrative” privilege.[*]Save the settings, restart MONyog service.

After following the above steps try to access the file which is shared across network.

NOTE: The shared path should be accessed with UNC notation (\systemshare). MONyog cannot identify if destination of the log file is on a Mapped Network Drive (this is a restriction with services on Windows and not with MONyog).

[Sayan Chaliha]

No probs. If you haven't posted in the SQLyog Forums yet, I can move this post for you…

[Sayan Chaliha]

Awesome, so we're on the same page! Discussed this with management few minutes back, so you can expect this feature post 4.0 GA (currently 4.0 is in beta). All of us have our plates full till 4.0 GA is out!

[Sayan Chaliha]

You know, from your suggestion, another idea just came to me: Would a feature which allows you to configure MONyog to fire an external script when a particular event occurs be helpful/practical from a user's perspective?

[Sayan Chaliha]

Hey Marcel,

Yes, supporting SMS/Jabber etc is actually a good idea. Let me add that to our wish-list for MONyog. Although you'll definitely see such a feature in MONyog in the future I can't give you an exact time now…

Thanks for your interest in MONyog!

[Sayan Chaliha]

Hi William,

We've put your request for a feature on our wish-list. You'll definitely see it in one of the future versions of MONyog; I'll keep you updated on that as well!

[Sayan Chaliha]

Hey William,

I'll have get back to you on that one; will have to discuss this with the rest of team as well. I'll keep you updated on that.

[Sayan Chaliha]

Hey Shawn,

For security reasons, you shouldn't be modifying the INI file directly. Instead use MONyog's interface. Once MONyog has started, from the local machine where MONyog is running access MONyog's interface (you can open port 5555 temporarily to do this). Then navigate to 'Tools' –> 'Preferences' –> 'Change Port' to change the default port to whatever suits you.

[Sayan Chaliha]

Hi William,

Firstly, here's a quick little tutorial on the MySQL bit of the MOM:

— MONyog executes SHOW GLOBAL STATUS and SHOW GLOBAL VARIABLES on MySQL

— For each of the variable/status returned by MySQL, a Javascript object is created in the MOM

— So basically you have:

Code:

MONyog.MySQL.GlobalVariables.
MONyog.MySQL.GlobalStatus.

I don't think there are any global variables/status that keep track of individual table sizes. The 'Disk Info' component is completely separated from 'Monitors/Advisors' and they don't share any information. Maybe we could build a feature which allows you to set alerts for databases/tables in 'Disk Info'. Sound like a good idea?

[Sayan Chaliha]

Hi Xeonfeng,

The problem here is that MONyog has to be started in the context of its bin directory. I'd suggest you use the start-up script, MONyog, to start and stop MONyog. So try typing in:

Code:

~$ ./Downloads/MONyog/bin/MONyog start

What you're doing isn't fully incorrect though. All you need to do 'cd' into the bin directory before executing MONyog-bin. Alternatively you can also try adding MONyog's bin directory to the environment variable LD_LIBRARY_PATH.

So there… you have a whole lot of solutions you can try out! Thank you for using MONyog!

[Sayan Chaliha]

Hi Steed,

To answer your questions briefly:

— MONyog's Dashboard displays the number of statements executed on the server being monitored, and not how many records these statements modified/inserted/deleted.

— Number of records added to/removed from a table in MySQL has no direct correspondence to the number of INSERT/DELETE statements executed on the server. A single INSERT may add multiple records to a table; a single DELETE statement may delete an entire table with thousands of records — They are still counted as 1 statement.

— MONyog uses SHOW GLOBAL STATUS and SHOW GLOBAL VARIABLES to collect server-wide stats. So if you're unsure if MONyog is displaying the right stats, you could always cross-check by executing these queries directly on your MySQL server. For example, the number of INSERT statements executed on your MySQL server can be found through:

Code:

mysql> SHOW GLOBAL STATUS LIKE 'Com_insert';
+——————-+————+
| Variable_name | Value |
+——————-+————+
| Com_insert | 102384 |
+——————-+————+
1 row in set (0.00 sec)

mysql>

Add to this the value of 'Com_replace' and you effectively get the number of INSERT statements that were executed on your server.

[Author]

Posts