[ 
https://issues.apache.org/jira/browse/HBASE-12455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-12455:
--------------------------
    Attachment: 12455.v2.txt
                with_descriptions.json
                raw.json

Thanks for the prompt [~eclark]

This should do.  It prints out descriptions if they are non-null and if they 
are not the same as the attribute name.

I've uploaded what a page looks like now and then what happens when you ad 
'?description=true'.  If I get a +1, I'll commit and update refguide at same 
time.  Will file follow-on issue to go over the metrics descriptions to add 
info where descriptions are unclear and to add some where they are missing.

> Add 'description' to bean and attribute output when you do 
> /jmx?description=true
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-12455
>                 URL: https://issues.apache.org/jira/browse/HBASE-12455
>             Project: HBase
>          Issue Type: Improvement
>          Components: metrics
>            Reporter: stack
>             Fix For: 2.0.0, 0.99.2
>
>         Attachments: 12455.txt, 12455.v2.txt, raw.json, with_descriptions.json
>
>
> Its hard figuring what our metrics mean. Each attribute and bean actually has 
> a description but its hard to get at. In mission control, etc., you have to 
> click on each attribute to see the description. Its painful.  Because the 
> description is rarely read, they are not as info-full as they could be.
> If you do /jmx in the UI, you get a dump of all beans associated with the 
> server but its just the attribute/bean name + value. The description is there 
> but its not displayed. We should give option to display descriptions. It 
> would be good for those exploring what metrics are available.  We actually 
> point folks at jvisualvm in the refguide to figure what metrics are 
> available.  Would be useful if we could point them at something that was 
> easier to navigate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to