[
https://issues.apache.org/jira/browse/HBASE-12455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206937#comment-14206937
]
stack commented on HBASE-12455:
-------------------------------
Here is what it looks like:
{code}
"name" : "Hadoop:service=HBase,name=JvmMetrics",
"description" : "JVM related metrics etc.",
"modelerType" : "JvmMetrics",
"tag.Context" : {
"description" : "Metrics context",
"value" : "jvm"
},
"tag.ProcessName" : {
"description" : "Process name",
"value" : "Master"
},
"tag.SessionId" : {
"description" : "Session ID",
"value" : ""
},
"tag.Hostname" : {
"description" : "Local hostname",
"value" : "localhost"
},
"MemNonHeapUsedM" : {
"description" : "Non-heap memory used in MB",
"value" : 35.50473
},
"MemNonHeapCommittedM" : {
"description" : "Non-heap memory committed in MB",
"value" : 36.3125
},
"MemNonHeapMaxM" : {
"description" : "Non-heap memory max in MB",
"value" : 130.0
},
"MemHeapUsedM" : {
"description" : "Heap memory used in MB",
"value" : 51.15728
},
"MemHeapCommittedM" : {
"description" : "Heap memory committed in MB",
"value" : 247.5
},
"MemHeapMaxM" : {
"description" : "Heap memory max in MB",
"value" : 4029.5
},
"MemMaxM" : {
"description" : "Max memory size in MB",
"value" : 4029.5
},
"GcCountParNew" : {
"description" : "GC Count for ParNew",
"value" : 7
},
"GcTimeMillisParNew" : {
"description" : "GC Time for ParNew",
"value" : 67
},
"GcCountConcurrentMarkSweep" : {
"description" : "GC Count for ConcurrentMarkSweep",
"value" : 0
},
"GcTimeMillisConcurrentMarkSweep" : {
"description" : "GC Time for ConcurrentMarkSweep",
"value" : 0
},
"GcCount" : {
"description" : "Total GC count",
"value" : 7
},
"GcTimeMillis" : {
"description" : "Total GC time in milliseconds",
"value" : 67
},
"ThreadsNew" : {
"description" : "Number of new threads",
"value" : 0
},
"ThreadsRunnable" : {
"description" : "Number of runnable threads",
"value" : 38
},
"ThreadsBlocked" : {
"description" : "Number of blocked threads",
"value" : 0
},
"ThreadsWaiting" : {
"description" : "Number of waiting threads",
"value" : 122
},
"ThreadsTimedWaiting" : {
"description" : "Number of timed waiting threads",
"value" : 51
},
"ThreadsTerminated" : {
"description" : "Number of terminated threads",
"value" : 0
},
"LogFatal" : {
"description" : "Total number of fatal log events",
"value" : 0
},
"LogError" : {
"description" : "Total number of error log events",
"value" : 0
},
"LogWarn" : {
"description" : "Total number of warning log events",
"value" : 0
},
"LogInfo" : {
"description" : "Total number of info log events",
"value" : 0
}
{code}
> 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
> Assignee: stack
> Fix For: 2.0.0, 0.99.2
>
> Attachments: 12455.txt, 12455.v2.txt, 12455.v2.txt, 12455.v3.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)
