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-3034) Improve the Monitor
Date Thu, 31 Jul 2014 16:48:39 GMT

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

Josh Elser commented on ACCUMULO-3034:
--------------------------------------

ACCUMULO-3005 is a first step towards the larger goal of decoupling the application logic
from the view logic. Using dropwizard gets us closer to using Jersey/Jetty/Jackson which are
likely the best candidates for technology that we want to leverage. While there are undeniably
downsides in how dropwizard works for our application, I still think it's a step in the right
direction. It starts us thinking about how we present metrics data from Accumulo and being
to codify some methods around them.

We can later come back and much more easily wire up all of the embedded jetty, jersey, and
jackson libs to get us what we want without the assumptions that dropwizard makes that are
undesirable.

> Improve the Monitor
> -------------------
>
>                 Key: ACCUMULO-3034
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3034
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> I thought it would be helpful to write up an umbrella issue to track the improvements
that we can make to the monitor to help satisfy a bunch of use cases.
> Presently I see the following issues with the monitor:
> * Untestable application logic
> * Manual HTML generation
> * Lack of programmatic interface for external consumers
> * Inability to deploy in other application servers
> * Responsiveness of the monitor tied to availability of Accumulo
> I'd like to see the solved with the following:
> * Application-level information provided as REST service (decoupled from views)
> * Templating library for generation of HTML
> * HTML pages use REST service to acquire data to populate the content
> * Definition of "API" for data returned by REST service, introduces typical "public API"
guarantees on data returned by the monitor REST
> * The ability to create packaging that be dropped into an existing application server
_without_ forcing this on users (embedded server should still be the default)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message