Red Hat Bugzilla – Bug 801186
postgres plugin Query resource cannot obtain metric
Last modified: 2014-10-23 08:29:42 EDT
+++ This bug was initially created as a clone of Bug #801167 +++
using the postgres Query resource type, I'm defining everything correctly, but the metric value isn't coming through.
I think its because the metric propery name is metricColumn (camel case) but hte jdbc metadata that gets returned is all the same case (metriccolumn) and when doing a case-sensitive search in a map for "metricColumn", it fails on lookup (and that's how it gets the value of the column data). This is a guess, but I think that's what is going on.
--- Additional comment from email@example.com on 2012-03-07 16:00:23 EST ---
I was totally wrong in my guess of what's going on.
Turns out, the metric query should return one row, TWO columns - in this case, the first column must have the value 'metricColumn' (literally) and the second is the numeric value.
select 'metricColumn', count(id) from my_table
is one example.
I did tweek the code slightly to support the use case where you don't want to supply a metric query and I allow for the name/description to be optional. I also added some debug log messages. But the core functionality was already there and working.
So, this should be considered a doc issue more than anything. We need better docs to explain how to use this resource.
--- Additional comment from firstname.lastname@example.org on 2012-03-07 16:07:00 EST ---
master git commit: 0910465
for information on this, see:
Added in the monitoring doc here:
Verified on 3.1.1.CR2. Created query to monitore number of alarms.