accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1013) integrate with a scalable monitoring tool
Date Mon, 09 Jun 2014 18:37:02 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025507#comment-14025507
] 

Josh Elser commented on ACCUMULO-1013:
--------------------------------------

The more I've been thinking about this, the more I'm leaning towards trying to migrate the
"monitor" into some REST service and rehash the GUI to use that service instead of making
direct calls to Accumulo. This would provide an interface to monitoring consumers that isn't
reliant on JMX (or some process that can convert the JMX for you like jmxtrans). It would
also make it infinitely easier to write tests to ensure that we're returning correct metrics.
Something that packages into a WAR would also be nice as it could be deployed into an existing
application server (not sure if we had a ticket specifically for that elsewhere).

Lots of alternatives for writing a webservice too: dropwizard, jersey, jax-rs initially come
to mind.

> integrate with a scalable monitoring tool
> -----------------------------------------
>
>                 Key: ACCUMULO-1013
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1013
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: monitor
>            Reporter: Eric Newton
>            Priority: Minor
>              Labels: gsoc2013, mentor
>             Fix For: 1.7.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.2#6252)

Mime
View raw message