[
https://issues.apache.org/jira/browse/HADOOP-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036861#comment-13036861
]
Robert Joseph Evans commented on HADOOP-7144:
---------------------------------------------
Just a quick note, I read through the code for the JMXProxy and it is a plain
text format, not JSON or XML.
It only supports GET but that can be be modified with a
?set&attr=<KEY>&val=<VALUE> to set an attribute; ?get&attr=<KEY> to get a
specific attribute; or ?qry=<QUERY> to output all attributes who's names match
the query using the mBeanServer.queryNames method. the default is ?qry=*:* if
nothing else if given.
> Expose JMX with something like JMXProxyServlet
> -----------------------------------------------
>
> Key: HADOOP-7144
> URL: https://issues.apache.org/jira/browse/HADOOP-7144
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Luke Lu
> Assignee: Luke Lu
> Labels: jmx
> Fix For: 0.23.0
>
> Attachments: HADOOP-7411-trunk-alpha.patch
>
>
> Much of the Hadoop metrics and status info is available via JMX, especially
> since 0.20.100, and 0.22+ (HDFS-1318, HADOOP-6728 etc.) For operations staff
> not familiar JMX setup, especially JMX with SSL and firewall tunnelling, the
> usage can be daunting. Using a JMXProxyServlet (a la Tomcat) to translate JMX
> attributes into JSON output would make a lot of non-Java admins happy.
> We could probably use Tomcat's JMXProxyServlet code directly, if it's already
> output some standard format (JSON or XML etc.) The code is simple enough to
> port over and can probably integrate with the common HttpServer as one of the
> default servelet (maybe /jmx) for the pluggable security.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
