| Bug #30820 | Monitor can't get disk information | ||
|---|---|---|---|
| Submitted: | 5 Sep 2007 8:25 | Modified: | 28 Jan 2009 14:55 |
| Reporter: | mantani shigeki | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Advisors/Rules | Severity: | S3 (Non-critical) |
| Version: | 1.1.1.5780 | OS: | Any |
| Assigned to: | Darren Oldag | CPU Architecture: | Any |
| Tags: | mer 121 | ||
[5 Sep 2007 8:47]
Sveta Smirnova
Thank you for the report. Verified as described.
[12 Sep 2007 20:50]
Peter Lavin
Added to "Known Issues".
[9 Nov 2007 11:50]
Eric Herman
Also, we only report information on / if the mysqld datadir is not on root this value is not very useful.
[19 Apr 2008 0:19]
Gary Whizin
Investigate instance iteration
[16 Jan 2009 17:27]
Marcos Palacios
Verified fixed in build 2.0.3.7134. NOTES: The value to be used in the 'Instance' field is different if we are using Data Item 'os:disk:disk_reads' vs 'os:fs:fs_unused'. Mainly notice the difference between using 'disk' and 'fs'. The following Variable Assignment examples show what works for these two type names. Example 1 (on Mac OSX): Variable: %disk_reads% Data Item: os:disk:disk_reads Instance: /dev/disk0s2 Example 2 (on Mac OSX): Variable: %fs_unused% Data Item: os:fs:fs_unused Instance: / Example 3 (on Windows XP): Variable: %fs_unused% Data Item: os:fs:fs_unused Instance: C:\ --
[28 Jan 2009 14:55]
Tony Bedford
An entry was added to the 2.0.3 changelog: When a custom rule requiring disk information was created, for example: [Expression] %disk_reads% > THRESHOLD [Thresholds] Critical Alert: 9000 Warning Alert: 3000 Info Alert: 1000 [Variable Assignment] variables: %disk_reads% Data Item: os:disk:disk_reads Instance: / The following error was written to the file mysql-service-agent.log: 2007-09-05 17:11:00: (critical) disk-get failed for c0d0p1: 2 It therefore appeared that the Service Agent was not able to obtain the required information.
Description: I created the custom rule like these. [Expression] %disk_reads% > THRESHOLD [Thresholds] Critical Alert: 9000 Warning Alert: 3000 Info Alert: 1000 [Variable Assignment] variables: %disk_reads% Data Item: os:disk:disk_reads Instance: / But this error was written in "mysql-service-agent.log". 2007-09-05 17:11:00: (critical) disk-get failed for c0d0p1: 2 This looks like NMAS can't get information. How to repeat: Create the rule as described previously. Read the "mysql-service-agent.log".