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
>
>Sreenivas Munnangi wrote on 9/24/09 7:37 PM:
>
>
>>No, the initial purpose of having enable-monitoring command without any
>>options is to attach btrace-agent and we prefer to keep that behavior.
>>
>>Bill Shannon wrote:
>>
>>
>>>Sreenivas Munnangi wrote on 9/24/09 3:04 PM:
>>>
>>>
>>>
>>>>>>Prashanth suggested that we can have 'all' option to set the level for
>>>>>>all modules at once without specifying each, for ex.
>>>>>>
>>>>>>enable-monitoring --modules all=LOW // this will set level to 'LOW' for
>>>>>>all modules
>>>>>>
>>>>>>enable-monitoring --modules all // this will set level to 'HIGH' for all
>>>>>>modules
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>Shouldn't the latter be the default?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>You mean if 'all' is not specified that should be taken as default, like
>>>>the one below
>>>>
>>>>enable-monitoring --modules
>>>>
>>>>
>>>>
>>>No, just "asadmin enable-monitoring".
>>>
>>>Equivalent to "asadmin enable-monitoring --modules all",
>>>equivalent to "asadmin enable-monitoring --modules all:HIGH".
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>>For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>
>>>
>>>
>>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
>
>