Sreenivas Munnangi wrote:
> Bill Shannon wrote:
>> Prashanth Abbagani wrote on 9/24/09 9:42 PM:
>>
>>> 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
>>>
>>
>> So it sounds like if I just do enable-monitoring, I don't actually get
>> any monitoring, right? Wouldn't it be more useful if enable-monitoring
>> enabled *all* monitoring if no modules were specified?
>>
> Pl. see my other response.
>
> Just to summarize, enable-monitoring does more than enabling module
> level monitoring and that includes
> - starting btrace-agent
> - registering probe-providers (useful for dTrace and client-script
> even if no stat providers exist)
> - register stats providers for the modules which already have set
> their monitoring level different from 'OFF'
Seems has if enable-monitoring is only used after monitoring has been
disabled, right? Sort of like the deployment enable command. Monitoring
is enabled by default, so user would only run enable-monitoring to
reenable it. In neither case are the levels set for the modules
affected, but no monitoring happens after disable-monitoring even though
monitoring levels for modules are set to HIGH or LOW.
In what case would I disable monitoring?
I assume I get a message if I run enable-monitoring when monitoring is
not disabled.
>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>>
>