admin@glassfish.java.net

Re: REVIEW:: monitor, enable-monitoring, disable-monitoring, monitoring concepts

From: Sreenivas Munnangi <Sreenivas.Munnangi_at_Sun.COM>
Date: Tue, 29 Sep 2009 11:39:40 -0700

Sankar Neelakandan wrote:
> Sreeni,
> Was your discussion with Bill changed anything other than
> discussed in this thread ?. Please let us know.
We discussed of some enhancements which will be filed as RFEs. I'll keep
you updated.
> thanks
> Sankar
>
> Sreenivas Munnangi wrote:
>> Bill,
>>
>> Let me see if I can state this clearly.
>>
>> At present, to set the module level, one need to use --modules option.
>>
>> If the --modules option is not specified, do you think that we should
>> set all module levels to "HIGH" ?
>>
>> I can drop by your office in the morning tomorrow.
>>
>> thanks
>> sreeni
>>
>> Bill Shannon wrote:
>>> Sreenivas Munnangi wrote on 9/24/09 9:45 PM:
>>>
>>>> Bill Shannon wrote:
>>>>
>>>>> So if I do enable-monitoring without specifying any modules, what
>>>>> monitoring have I enabled? None?
>>>>>
>>>>>
>>>> following happens
>>>> - btrace-agent is attached
>>>> - probe-providers are registered
>>>> - stat providers are registered depending on the existing module level
>>>> setting
>>>> - monitoring data is gathered by stats providers and ready for use by
>>>> clients CLI, GUI, REST,client-scripting, dTrace
>>>>
>>>> if monitoring is in disabled state, none of the above would have happened
>>>>
>>>
>>> Do I have to do enable-monitoring before using the monitor command
>>> to view the statistics?
>>>
>>> I guess I'm just not getting it. If enable-monitoring doesn't set
>>> the monitoring level for any modules, what things are collecting
>>> data for use by the CLI, GUI, etc.? Is there some minimum set of
>>> monitoring data that's collected even if all the modules are set
>>> to OFF?
>>>
>>> I'm trying to look at this from the perspective of someone who just
>>> wants to see some monitoring data. Most of what you said above seems
>>> like implementation details that I shouldn't need to care about.
>>> btrace-agent? probe-provider? Why do I need to know about any of that?
>>>
>>> It seems like the use case you have in mind is that I run around and set
>>> the dials for all the modules that I want to monitor, and then once I've
>>> got them all set I do "enable-monitoring" to start them collecting data
>>> and "disable-monitoring" to turn off the data collection but retain the
>>> settings. Which would mean "enable-monitoring" without having set any
>>> of the monitoring levels for any modules isn't going to do anything
>>> useful.
>>>
>>> I guess I'm still confused...
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>
>>>
>>