On 09/24/09 12:03 AM, Bill Shannon wrote:
> Sreenivas Munnangi wrote on 9/23/09 9:26 PM:
>
>> Bill Shannon wrote:
>>
>>> Dixie Pine wrote on 9/23/09 2:45 PM:
>>>
>>>
>>>> Greetings,
>>>>
>>>> I've attached PDFs of the v3 man pages for monitoring:
>>>> monitor, enable-monitoring, disable-monitoring, and the monitoring
>>>> concepts page
>>>> Please review.
>>>>
>>>> thanks,
>>>> Dixie
>>>>
>>>> The list-monitoring-levels command is not available yet. If it doesn't
>>>> make v3, I'll remove references to it in these man pages.
>>>>
>>>>
>>>>
>>> monitor.1:
>>>
>>> The attributes it tells you to set for different types, are they different
>>> than what can be enabled using enable-monitoring?
>>>
>>>
>> Yes, the --type does not exactly correspond to what can be enabled for
>> monitoring. This is borrowed from v2.
>>
>
> Do we want to recommend that people use "asadmin set" with the listed
> attributes, or "asadmin enable-monitoring"? I would've thought the
> latter.
>
User is so hoping for two separate ways:
* enable-monitoring, disable-monitoring, list-monitoring-levels
(which shows me all the current modules and their levels), monitor
* list-get-set
Then I can document the two ways in separate tasks. Masochists can use
the list-get-set way if they want to.
And what about showing statistics? The Admin Console is nice, but right
now the CLI method for showing statistics is less than wonderful. Any
chance of avoiding dotted names there too?
Dixie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
>