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...