Jaeger: iOS client library

[yurishkuro]

E.g. https://github.com/OutThereLabs/jaeger-client-objc by @pat2man

[swizzlr]

If anyone is actively working on this, let me know. Looking to build a Swift tracer in the near term.

[simonpierreroy]

@yurishkuro We have worked on it and release a first version of the project. You can take a look and give us feedback. :) https://github.com/wayfair/jaeger-swift

[yurishkuro]

before I do, what's the state of OpenTracing API for iOS? I only see https://github.com/opentracing/opentracing-objc. There's also https://github.com/lightstep/opentracing-swift, which looks like it's being worked on (cc @ryanrhee).

[ryanrhee]

opentracing-swift is ready for use, no further changes are planned.
On Fri, Jan 11, 2019 at 7:30 AM Yuri Shkuro [e-mail]
wrote:

before I do, what's the state of OpenTracing API for iOS? I only see
https://github.com/opentracing/opentracing-objc. There's also
https://github.com/lightstep/opentracing-swift, which looks like it's
being worked on (cc @ryanrhee https://github.com/ryanrhee).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jaegertracing/jaeger/issues/576#issuecomment-453280099,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOzdINjzGL9bpfIJuO-cBuBBbvtALH0ks5vB77ngaJpZM4QzYzl
.

[yurishkuro]

@ryanrhee are there plans to move it under opentracing org? cc @austinlparker

[austinlparker]

Lemme check.

[tedsuo]

Let's do it!

[ryanrhee]

@jmacd mentioned that we'd like to move this under the opentracing org, but I'm not sure what the current status of that is.

[jpkrohling]

What's the status of this one?

[austinlparker]

We still want to move it, but I don't have permissions to move things into opentracing.

[yurishkuro]

@austinlparker make me admin of that repo and I can move it

[austinlparker]

done

[yurishkuro]

Which one? I don't see Settings for https://github.com/lightstep/opentracing-swift

[austinlparker]

Try refreshing? It shows you as admin on the settings page.

[yurishkuro]

I needed to accept the invite. Move is done.

[austinlparker]

👍

[jmacd]

Cool! Thanks Yuri.

On Wed, Apr 3, 2019 at 2:59 PM Austin Parker [e-mail]
wrote:

👍

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jaegertracing/jaeger/issues/576#issuecomment-479674362,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADdiifsfrtV80h1ybV1prjQ7ymGUgFXTks5vdSRVgaJpZM4QzYzl
.

[simonpierreroy]

@yurishkuro We just released Jaeger-iOS for Swift-5 https://github.com/wayfair/jaeger-swift. We have been using it for 3 months in our codebase at Wayfair to help improve the performance of our mobile app. (We will soon publish a blog post about it) Let me know if you have any questions.

[ryanrhee]

@simonpierreroy1 did you write your own opentracing-swift interface? i don't see you using https://github.com/opentracing/opentracing-swift or https://github.com/opentracing/opentracing-objc .

[yurishkuro]

@simonpierreroy1 Great README in your repo! A few questions:

• Does it implement the API from https://github.com/opentracing/opentracing-swift ?
• It mentions you submit spans in JSON - which JSON schema are you using?
• Will you be interested in moving that repo to jaegertracing/jaeger-client-swift?
• Would you be able to license it with Apache v2 license?

[simonpierreroy]

@ryanrhee @yurishkuro

• API: We used our own interface, there was no official one in swift when we started working on that project in October. We created an API that could support Jaeger (and Zepkin in the future) or any type of new implementation of spans. We use “more abstract ideas and types” to represent open-tracing concepts than the ones enforced by the Thrift definition and we map it when serializing to disk or sending spans over a network.

Side note: The public and private interface are 100% documented https://wayfair.github.io/jaeger-swift. If you would like to see the public and private documentation, clone the repo and run jazzy --min-acl private.

• JSON schema: I can send you the JSON schema, but it is a one-to-one correspondence to https://github.com/jaegertracing/jaeger-idl/blob/master/thrift/jaeger.thrift.

• Moving the repo and Apache v2 license: Our legal team has requested that our repository stay under the wayfair namespace. If that is ok with you we would still love to be the official version. I can also ask them for the Apache v2 license.

[simonpierreroy]

Take a look here for more info on our work with Jaeger: https://tech.wayfair.com/2019/05/open-tracing-for-ios-a-performance-tool-for-everyone .

[yurishkuro]

@simonpierreroy1 great article!

[reinpold]

Take a look here for more info on our work with Jaeger: https://tech.wayfair.com/2019/05/open-tracing-for-ios-a-performance-tool-for-everyone .

@simonpierreroy1 Thank you for sharing this, it's very useful. Do I understand correctly that your client does not provide the functionality to inject a SpanContext into a carrier using Jaeger's propagation format? I am just wondering how you are propagating the SpanContext to downstream backend services currently?