[
https://issues.apache.org/jira/browse/ACCUMULO-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422711#comment-15422711
]
Dave Marion commented on ACCUMULO-1013:
---------------------------------------
FWIW, I added a StatsDSink to the Hadoop Metrics2 framework in HADOOP-12360.
One potential solution would be to [configure |
https://nationalsecurityagency.github.io/timely/docs/#collecting-metrics-from-hadoop-and-accumulo
] Hadoop and Accumulo to emit their metrics to a CollectD service and run a
[Timely| https://nationalsecurityagency.github.io/timely/] server.
> Integrate with a scalable monitoring tool
> -----------------------------------------
>
> Key: ACCUMULO-1013
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1013
> Project: Accumulo
> Issue Type: Sub-task
> Components: monitor
> Reporter: Eric Newton
> Priority: Minor
> Labels: gsoc2013, mentor
> Fix For: 1.9.0
>
>
> The monitor is awesome. It should die.
> I'm going to move other monitor tickets under this one (if I can), and create
> some requirement tickets.
> We would be better off putting our weight behind an existing monitoring
> program which can scale, if one exists.
> Hopefully we can combine tracing efforts and have a nicer distributed
> trace-based tool, too.
> For display functionality, lots of possibilities: Graphite, Cubism.js, D3.js
> (really, any number of really slick Javascript graphing libraries). For log
> collection, any number of distributed log management services out there too
> can serve as inspiration for functionality: statsd, logstash, cacti/rrdtool.
> Currently all of Accumulo monitoring information is exposed via JMX; a nice
> balance could be found leveraging the existing monitoring capabilities with
> JMXTrans (or equivalent) and applying a new GUI.
> Familiarity with Java and JMX would be ideal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
