[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-user
Subject:    RE: [configuration] Monitoring configs
From:       "Ahmad, Zeba" <zeba.ahmad () ebay ! com>
Date:       2016-05-03 4:50:29
Message-ID: F2A103712A9B92409340DE5F384BF9852F7B3A79 () DEN-EXDDA-S82 ! corp ! ebay ! com
[Download RAW message or body]

Hi Oliver, 

Thank you for the reply. I actually wanted the configurations to surface up as JMX \
beans by registering in the MBean server at the time of creating the Configuration \
object itself. 

For now we have decided to go with option (1) where user does this at their side by \
calling MBean register after creating Configuration, but also use your suggestion of \
event mechanism to reload the JMX bean in case the file changes. 

Regards,
Zeba
-----Original Message-----
From: Oliver Heger [mailto:oliver.heger@oliver-heger.de] 
Sent: Tuesday, April 26, 2016 1:10 AM
To: Commons Users List <user@commons.apache.org>
Subject: Re: [configuration] Monitoring configs



Am 25.04.2016 um 09:45 schrieb Ahmad, Zeba:
> Hi,
> 
> I'm looking at providing a platform for users to monitor their 
> configurations either via JMX or some other means. Some ways I can 
> think of doing this
> 
> 1)      Let users register their chosen configurations as MBeans. \
> Here's<https://github.com/Netflix/archaius/blob/master/archaius-core/src/main/java/com/netflix/config/jmx/ConfigJMXManager.java> \
> a similar approach by Netflix. Here however, platform cannot mandate all \
> configurations to get surfaced for monitoring. 
> 2)      Read all config files present for the given application in config \
> directory, use Apache Modeler or some other to dynamically generate bean \
> descriptors and JMX MBeans for monitoring. But here I'm duplicating the reading of \
> the configs and the memory structures. 
> 3)      Have instrumentation within apache-commons-config  for such monitoring by \
> JMX or any other means. 
> Reg. #3, is there any recommendation on how users can efficiently \
> monitor/view/modify their configurations dynamically (without delivering an updated \
> file)?

Not sure what you want to achieve exactly. Could the event mechanism [1] be of some \
help?

Oliver

[1]
http://commons.apache.org/proper/commons-configuration/userguide/howto_events.html#Events


> 
> Regards,
> Zeba
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]