MySQL Bugs: #41040: Not All Data Collection Items Available

Bug #41040	Not All Data Collection Items Available
Submitted:	25 Nov 2008 23:25	Modified:	10 Dec 2008 22:07
Reporter:	Mikiya Okuno	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Enterprise Monitor: Advisors/Rules	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Darren Oldag	CPU Architecture:	Any

Description:
os:load_averate can be found in the data collection items, and we can create custom advisor rules using it, but it is not be able to be scheduled. I fond that corresponding object is not defined in the service manager inventory.

mysql> select * from inventory_attributes where attribute_name like '%load%';
+--------------+---------+-----------------------+----------------+--------------+
| attribute_id | type_id | attribute_name        | attribute_type | insert_count |
+--------------+---------+-----------------------+----------------+--------------+
|          425 |       3 | have_dynamic_loading  | string         |            0 | 
|          554 |       3 | preload_buffer_size   | long           |            0 | 
|          589 |       3 | slave_load_tmpdir     | string         |            0 | 
|          775 |      58 | Com_load              | long_counter   |            0 | 
|          776 |      58 | Com_load_master_data  | long_counter   |            0 | 
|          777 |      58 | Com_load_master_table | long_counter   |            0 | 
|          780 |      58 | Com_preload_keys      | long_counter   |            0 | 
+--------------+---------+-----------------------+----------------+--------------+
7 rows in set (0.00 sec)

Unavailable variable should not be displayed in the menu. (See the attachment)

How to repeat:
Create a custom advisor using os:load_averageX

Suggested fix:
n/a

Screen shot: unavailable item is listed in the menu.

Attachment: Picture 6.png (image/png, text), 53.34 KiB.

os::loadavg is the 'namespace'::'type' of the object.  the attributes are "0", "1", and "2" corresponding to the three load average values available on most unixes.  generally they are the 1, 5, and 15 minute load averages, but this is not guaranteed and is system dependent.

root@localhost [em2]> select namespace, type_name, attribute_name, attribute_type from inventory_namespaces join inventory_types using (namespace_id) join inventory_attributes using (type_id) where type_name='loadavg';
+-----------+-----------+----------------+----------------+
| namespace | type_name | attribute_name | attribute_type |
+-----------+-----------+----------------+----------------+
| os        | loadavg   | 0              | double         | 
| os        | loadavg   | 1              | double         | 
| os        | loadavg   | 2              | double         | 
+-----------+-----------+----------------+----------------+

so, to use them in custom rules -- it must be 'supported' on the operating system in question.  so far, the only time i have not seen it supported is on a windows operating system, as windows does not expose these values from the OS itself.

can you say what operating system this was trying to be scheduled against?

I'm using MacOS X.

Do you actually get an error message when you try and schedule this custom rule? If so, could you add it to the bug report? If not, and you're deducing that the rule can't be scheduled from the query against the repository that you've posted, Darren explains why that would be.

An error message.

Attachment: Picture 12.png (image/png, text), 15.79 KiB.

Hi Mark,

I got a message like the attached above, and could not schedule a rule which includes os:loadavg. Kind regards!

I was able to create a rule using the os::loadavg->0 data collection.  i then scheduled it against an agent/mysqld successfully.  the rule fired, and I can an INFO alarm.

there are several things that could prevent this from working.

1) is the agent on the same host as the mysqld instance.  OS data items *only* work if they are local to the mysql instance.

2) win32 does not report loadavg (but i see you are on mac, so i don't think this is it).

3) in the Variable Assignment section, the "Instance" field must be set to "local" (no quotation marks).  this is the key to get the rule scheduled against the host that the mysql resides on.

i have a hunch it is #3 that is causing the problem, as that is not an obvious thing to know.

Hi Oldag,

I can repeat it on MacOS X, not win 32. And I installed agent on the same host to mysqld. What is the possible cause of this problem? Does SIGAR support os:loadavg on MacOS X?