| Bug #47033 | MEM Manual defines incorrect order for custom data collection item | ||
|---|---|---|---|
| Submitted: | 1 Sep 2009 4:26 | Modified: | 3 Sep 2009 7:19 |
| Reporter: | Jonathon Coombes | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Documentation | Severity: | S3 (Non-critical) |
| Version: | 2.0,2.1 | OS: | Any |
| Assigned to: | MC Brown | CPU Architecture: | Any |
[3 Sep 2009 7:19]
Enterprise Tools JIRA Robot
Martin MC Brown writes: Documentation has been updated to show the correct order

Description: <pre> <?xml version="1.0" encoding="utf-8"?> <classes> <class> <classname>innodb_min_free</classname> <namespace>mysql</namespace> <query><![CDATA[SELECT MIN(substring_index(substring_index(table_comment," ",3)," ",-1)/1024/1024) as Free FROM INFORMATION_SCHEMA.TABLES WHERE engine = 'InnoDB']]></query> </class> </classes> </pre> The order of the items in the example to create a custom data item is incorrect in the manual in 5.4.8.1. Creating and Using a Custom Data Item XML File. The example lists the order of the items as classname, namespace, query where the correct order is namespace, classname, query. How to repeat: Create a custom data item as suggested in the manual and the 2.1 agent gives errors. Suggested fix: Update to correct order.