Bug 1122514 - Query Resource only available in postgres Plugin
Summary: Query Resource only available in postgres Plugin
Keywords:
Status: ON_QA
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
: RHQ 4.13
Assignee: Thomas Segismont
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-23 12:10 UTC by Andre Rösner
Modified: 2014-07-24 12:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
plugin descriptor oracle plugin (38.72 KB, text/xml)
2014-07-23 12:10 UTC, Andre Rösner
no flags Details

Description Andre Rösner 2014-07-23 12:10:58 UTC
Created attachment 920205 [details]
plugin descriptor oracle plugin

Description of problem:
The rhq-plugin.xml of the oracle and the Mysql plugin don't contain the service element for the query resource.

Version-Release number of selected component (if applicable):
4.12

How reproducible:
add oracle server/mysql server, try to add Query resource

Steps to Reproduce:
1.
2.
3.

Actual results:
no import possible

Expected results:
import of query resource to gather sql based metrics

Additional info:
as decribed here (for other version and with postgres):
http://management-platform.blogspot.fr/2012/03/monitoring-custom-data-from-db-queries.html

i added the corrected rhq-plugin.xml (from https://raw.githubusercontent.com/rhq-project/rhq/master/modules/plugins/oracle/src/main/resources/META-INF/rhq-plugin.xml) for the oracle plugin (not tested yet)

Comment 1 Thomas Segismont 2014-07-23 13:09:38 UTC
Thanks Andre! I'll merge ASAP.

Comment 2 Thomas Segismont 2014-07-24 12:29:12 UTC
Fixed in master

commit d4ae35c7bcc77f9418600d5f3485e92d496a4026
Author: Thomas Segismont <tsegismo@redhat.com>
Date:   Thu Jul 24 14:27:17 2014 +0200
    
Added to the MySQL and Oracle plugins
    
Tested on Oracle XE and MariaDB


Note You need to log in before you can comment on or make changes to this bug.