htrace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: [DISCUSS] OpenTracing API implementation
Date Mon, 06 Mar 2017 18:36:13 GMT
What Colin said.
S

On Mon, Mar 6, 2017 at 10:32 AM, Colin McCabe <cmccabe@apache.org> wrote:

> Hi Konstantin,
>
> Just to be clear, you're proposing an adapter that allows people to use
> OpenTracing as the span creation API, and HTrace SpanReceivers to store
> spans?  That seems like an interesting idea and I don't think anyone
> would object to adding it.  It's just a matter of someone committing to
> write and maintain it.
>
> best,
> Colin
>
>
> On Mon, Mar 6, 2017, at 04:26, Konstantin Gribov wrote:
> > Hi, folks.
> >
> > Are you interested in OpenTracing API (OT) implementation with HTrace as
> > tracer target?
> >
> > As I saw in [1] there was a bit of interest for OT but from different
> > angle
> > (community-wise).
> >
> > Zipkin has both it's own Dapper-inpired API and OT API impl which gives
> > good way for API to be vendor neutral. Also Uber is opensourcing its
> > Jaeger
> > (which is native OT impl).
> >
> > I think, implementing OT API as separate module could bring more users to
> > HTrace and improve its adaption.
> >
> > If PMC is interested in it, I could give it a try.
> >
> > [1]:
> > https://lists.apache.org/thread.html/373c91d58dcb9c87e29ff4cb2ad4d3
> 39ec228fdf6155b2e6a09c23f6@1463677907@%3Cdev.htrace.apache.org%3E
> >
> > --
> >
> > Best regards,
> > Konstantin Gribov
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message