Răspuns: AS7 plugin: Hibernate Query Cache resource type
Thomas Segismont
tsegismo at redhat.com
Tue Dec 3 17:10:42 UTC 2013
My opinion is that Query Cache resources should not be auto discovered
whereas JMS queues should be.
Waiting for more input before taking action.
Le 29/11/2013 12:49, Michael Burman a écrit :
> Hi,
>
> Costel, on the other hand, JMS queues and their changing sizes are the
> only thing we really monitor in our environment. That's a quick way to
> find out if something is wrong, when queue's message amounts keep
> growing (or a certain service shows such behaviour).
>
> There's no silver bullet to keep just certain resources.
>
> - Micke
>
>
> On Fri, Nov 29, 2013 at 1:17 PM, Costel Cosman <costelcsmn at yahoo.ro
> <mailto:costelcsmn at yahoo.ro>> wrote:
>
> Hi Thomas,
>
> I was thinking the same thing with other resources too, like the
> EJBs, JMS queues, etc.
>
> In our company we use RHQ to monitor production JBoss servers with a
> lot of EJBs but no one is really interested to monitor these EJBs or
> at least they are interested in monitoring only some of them.
> These useless resources bring unnecessary load on both RHQ server
> and agent. By default they are checked for the availability and have
> some metrics enabled.
>
> An idea would be to have a lazy discovery for these resources - at
> request, maybe some configuration in the Connection Settings of the
> parent resource to enable the discovery of such child resources,
> maybe define a regexp pattern for the resource names we are
> interested in.
>
>
> Regards,
> Costel
>
>
> ------------------------------------------------------------------------
> *De la:* Thomas Segismont <tsegismo at redhat.com
> <mailto:tsegismo at redhat.com>>
> *Către:* rhq-devel at lists.fedorahosted.org
> <mailto:rhq-devel at lists.fedorahosted.org>
> *Trimis:* Vineri, 29 Noiembrie 2013 12:27:48
> *Subiect:* AS7 plugin: Hibernate Query Cache resource type
>
> Hi everyone,
>
> I fixed "Bug 1033130 - [AS7] Exception during discovery of Query Cache
> resources of RHQ Server resource" this week.
>
> So what? Well now if you inventory RHQ server resource you get more
> than
> 2000 query cache resources showing up. Which of course costs you CPU
> and
> memory.
>
> You can of course just ignore this resource type (via the admin pages).
>
> So I was wondering: shouldn't we change such resource types to no
> longer
> auto discover them but only allow manual add?
>
> Opinions?
>
> Thanks,
> Thomas
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> <mailto:rhq-devel at lists.fedorahosted.org>
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>
>
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> <mailto: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