Răspuns: Disabled metrics are still collected

Larry O'Leary loleary at redhat.com
Mon Mar 10 18:19:57 UTC 2014


That case does seem different.

In my case the metrics are disabled and always have been disabled. The
only measurement change was enabling and setting the collection interval
of completely unrelated metrics.

This is from RHQ 4.9. But perhaps this issue has always been present. I
don't think one would really ever see it unless you were looking at
debug logging at the time an unexpected exception occurred during
measurement collection or if you were looking at the measurement
schedules sent to the getValues method.

>From the server side it appears that these metrics won't be reported or
show up because they are disabled.
-- 
Larry O'Leary
https://plus.google.com/+LarryOLeary


On Mon, 2014-03-10 at 16:04 +0000, Costel Cosman wrote:
> Hi, 
> 
> I don't know if this is related with this use case, but, at some
> point, I encountered a similar case using RHQ 4.7 when some
> measurement collection intervals defined in the RHQ Server were not
> updated/synchronized in the agent plugin container.
> 
> Unfortunately I couldn't reproduce the use-case, the measurement
> collection intervals didn't want to update at agent restart. 
> 
> To fix the problem, I had to change again the values with RHQ GUI in
> order to get synchronized on the agent side.
> 
> 
> 
> I remember there was a similar issue some time ago but I know that it
> was fixed.
> 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=741971
> 
> 
> Regards,
> Costel
> 
> 
> 
> 
> 
> 
> 
> ______________________________________________________________________
> De la: Larry O'Leary <loleary at redhat.com>
> Către: RHQ Dev List <rhq-devel at lists.fedorahosted.org> 
> Trimis: Luni, 10 Martie 2014 17:20:37
> Subiect: Disabled metrics are still collected
> 
> 
> While looking into another issue dealing with metric collection
> failures, I have stumbled across something strange. I can see metrics
> being collected by the agent for metrics which are not enabled. Is
> this
> expected? 
> 
> In my case I am working with a non-Tx datasource resource from the AS7
> plug-in. Even though many of the metrics are disabled by default, I am
> seeing some disabled metrics included in the measurement collection
> request:
> 
> PreparedStatementCacheCurrentSize
> PreparedStatementCacheMissCount
> PreparedStatementCacheMissCount
> PreparedStatementCacheAddCount
> PreparedStatementCacheAccessCount
> PreparedStatementCacheAccessCount
> PreparedStatementCacheDeleteCount
> PreparedStatementCacheDeleteCount
> PreparedStatementCacheHitCount
> PreparedStatementCacheHitCount
> AverageBlockingTime
> AverageCreationTime
> MaxCreationTime
> TimedOut
> TotalCreationTime
> TotalCreationTime
> TotalBlockingTime
> TotalBlockingTime
> 
> 
> If this is happening with other resources and resource types, I can
> imagine that the load generated on and by the agent is much higher
> then
> what would be expected.
> 
> http://ur1.ca/gt6mv contains the log message showing these disabled
> metrics being included in the getValues call. Something to note is
> that
> even though the above metrics are disabled, the PC reports them as
> enabled as seen in the log message.
> 
> Is this expected? A bug? Something we are already aware of?
> -- 
> Larry O'Leary
> https://plus.google.com/+LarryOLeary
> 
> 
> 
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
> 
> 
> 
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel



More information about the rhq-devel mailing list