accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Young (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3903) Add ability for Accumulo to store and display external Htrace traces in the Monitor pages
Date Tue, 16 Jun 2015 16:56:01 GMT

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

Philip Young commented on ACCUMULO-3903:
----------------------------------------

Not sure whether I really want to tie this into the refactoring of the Accumulo monitor work,
but it sort of suggests that this work needs to take into account the overall direction of
what people think should happen to the monitor.

It seems like from the outside looking in that there are two possibly competing directions
between 1) getting rid of the monitor entirely and redistributing the functionality to other
third party tools (ACCUMULO-1013) and 2) redeveloping the Monitor in a more modern webapp
framework (ACCUMULO-3005). It seems that there needs to be some consensus on this issue and
as a result would inform the implementation of this ticket (otherwise you could waste time
doing a whole bunch of work).



> Add ability for Accumulo to store and display external Htrace traces in the Monitor pages
> -----------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3903
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3903
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: monitor, trace
>            Reporter: Philip Young
>            Priority: Minor
>              Labels: features
>
> I would like to use Accumulo as the central store of trace information for my whole system
(of which Accumulo is also a component). I am currently integrating the existing Accumulo
HTrace trace implementation into one of the other components of my system. I would imagine
that this would be also useful for other people to use in tracing their whole system.
> As such, I would like to be able to use the existing trace pages in the Monitor for displaying
all these traces. I would like to add the ability to filter the traces that are displayed
to particular system components (services) and/or hosts. This could be implemented using either
a drop down or filter textbox to filter client-side the already de-serialised records.
> There are a number of existing tickets that relate to this work that could be done as
part of this work which would centrally position Accumulo as an enabler for tracing functionality
for a whole system, they include:  
> # [ACCUMULO-1198|https://issues.apache.org/jira/browse/ACCUMULO-1198]
> # [ACCUMULO-1013|https://issues.apache.org/jira/browse/ACCUMULO-1013]
> # [ACCUMULO-3005|https://issues.apache.org/jira/browse/ACCUMULO-3005]
> Also, even though the Accumulo Trace implementation can be used by other components pretty
much straight out of the box, it does require the accumulo-site.xml file for it to work. This
probably could be refactored to not require all the site.xml for the trace server to work
but some other trace config file. 
> Thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message