[
https://issues.apache.org/jira/browse/HTRACE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278897#comment-15278897
]
Colin Patrick McCabe commented on HTRACE-362:
---------------------------------------------
Thanks, [~nisala12]. I think Kudu will be great as an HTrace span receiver.
I think the most difficult part of this project will be hooking up the existing
HTrace web UI to the new Kudu-based span receiver. I can see at least two ways
of doing that:
1. Add some code to htraced to allow it to store and retrieve data from Kudu.
2. Create a new standalone web server in htrace-kudu which can talk to Kudu.
3. Integrate the htrace web UI into Kudu itself.
The first approach would require htraced to wrap the C APIs of Kudu. It
shouldn't be too hard to do this from Go, since Go has a pretty good foreign
function interface (FFI) for C.
The second approach might require us to run something like a Tomcat or Jetty
web server. This web server would have to implement the same REST API as
htraced, so that we could use the same Javascript code for both. Alternately,
we could serve slightly different Javascript, but that would be complex and
somewhat difficult to maintain, I think.
I don't think the third approach is that practical. Kudu is a separate project
and this user interface logically belongs to HTrace, not to Kudu.
> Apache KUDU Span receiver implementation for Apache HTrace
> ----------------------------------------------------------
>
> Key: HTRACE-362
> URL: https://issues.apache.org/jira/browse/HTRACE-362
> Project: HTrace
> Issue Type: Bug
> Reporter: Nisala Mendis
> Assignee: Nisala Mendis
> Attachments: kudu_span_receiver_basic_design.pdf
>
>
> Implementation should be carried two components as span receiver that writes
> kudu back end and span viewer to view written span/traces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
