Bill Shannon wrote:
> So if I do enable-monitoring without specifying any modules, what
> monitoring have I enabled? None?
>
Following are the different levels, when you give none, then you are
affecting the attribute 'monitoring-enabled'. Along with that, you could
choose to set the individual container monitoring levels.
configs.config.server-config.monitoring-service.dtrace-enabled=false
configs.config.server-config.monitoring-service.mbean-enabled=true
*configs.config.server-config.monitoring-service.monitoring-enabled=true*
configs.config.server-config.monitoring-service.module-monitoring-levels.connector-connection-pool=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.connector-service=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.ejb-container=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.http-service=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jdbc-connection-pool=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jersey=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jms-service=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jpa=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jvm=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.orb=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.security=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.thread-pool=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.transaction-service=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.web-container=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.web-services-container=OFF
>
> 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
>>>
>>>
>>>
>
>