accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1013) Integrate with a scalable monitoring tool
Date Tue, 18 Aug 2015 16:01:47 GMT


Josh Elser commented on ACCUMULO-1013:

bq. Personally I would like to see some API where I can provide an implementation to get the
metrics off of each tserver and into some type of external monitoring tool

If you haven't noticed yet, the Hadoop Metrics2 support in 1.7.0 (I think...) does allow you
to register custom sinks (aka a collector) that all of the existing metrics will be sent to
automatically. For example, this is how Ambari gets metrics and draws pretty graphs about
what Accumulo is doing.

> Integrate with a scalable monitoring tool
> -----------------------------------------
>                 Key: ACCUMULO-1013
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: monitor
>            Reporter: Eric Newton
>            Priority: Minor
>              Labels: gsoc2013, mentor
>             Fix For: 1.8.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
> 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,
> 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

View raw message