Bug 1147930 - Notify resource components when metric schedules changed
Summary: Notify resource components when metric schedules changed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Agent
Version: JON 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER05
: ---
Assignee: Libor Zoubek
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-30 10:38 UTC by Libor Zoubek
Modified: 2015-11-02 00:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-30 13:58:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1029409 0 unspecified CLOSED Auto-enable ejb3 statistics when a user requests calltime metrics for EJBs 2021-02-22 00:41:40 UTC

Internal Links: 1029409

Description Libor Zoubek 2014-09-30 10:38:18 UTC
Description of problem:
In order to implement Bug 1029409 we need some mechanism to notify plugins about updated schedules. Fortunately there's already a "message" sent from server to agent when measurement schedules change.

The idea is to introduce new Listener interface that would be implemented by ResourceComponent classes. Agent internal code would invoke this interface whenever it recieved a request from server about updated metric schedules. 

This approach has a drawback. Resource component would get invoked many times on many agents in case user changes/enables metric schedule on resource type level.

On the other hand it gives a plugin writer a way to implement this listener per resource (if given metric was enabled on resource A and stays disabled on B, plugin can configure managed resource to "produce" metric for resource A only)

AS7 plugin can implement this interface just by checking whether global EJB3 statistics are enabled and would enable it eventually.

Additional info:

Comment 1 Libor Zoubek 2014-09-30 13:58:23 UTC
Based on discussion with mazz and Heiko, we don't need this implemented.


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