Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Zipkin exporter mappings #220

Closed
hekike opened this issue Aug 18, 2019 · 4 comments
Closed

Zipkin exporter mappings #220

hekike opened this issue Aug 18, 2019 · 4 comments
Assignees
@hekike
Labels
area:sdk Related to the SDK area:semantic-conventions Related to semantic conventions spec:trace Related to the specification/trace directory
Milestone
v0.6

Comments

@hekike
Copy link
Member

hekike commented Aug 18, 2019 •
edited
Loading

While working on the opentelemetry-javascript Zipkin exporter, I run into a couple of questions around expected mapping between OpenTelemetry Span(s) and Zipkin Span(s).

Here is the list of things I found:

  • SpanKind.INTERNAL doesn't exist in Zipkin
  • Status concept doesn't exist in Zipkin
  • Event doesn't support Attribute(s) in Zipkin

Related PR: open-telemetry/opentelemetry-js#192

I also took an initial stab on a spec proposal: #221
This was referenced Aug 18, 2019
Closed
Merged
@SergeyKanzhelev SergeyKanzhelev added this to the Alpha v0.2 milestone Sep 27, 2019
@SergeyKanzhelev
Copy link
Member

@hekike do you think you can work on your PR this week? Do you need help?

@bogdandrutu bogdandrutu modified the milestones: Alpha v0.2, Alpha v0.3 Oct 10, 2019
@SergeyKanzhelev SergeyKanzhelev mentioned this issue Dec 10, 2019
Merged
@jmacd
Copy link
Contributor

jmacd commented Jan 22, 2020

This will close with #380.

@carlosalberto
Copy link
Contributor

Moving this to the next milestone.

@carlosalberto carlosalberto modified the milestones: Alpha v0.3, Alpha v0.4 Jan 29, 2020
@SergeyKanzhelev SergeyKanzhelev mentioned this issue Feb 18, 2020
Merged
@carlosalberto carlosalberto modified the milestones: v0.5, v0.6 Jun 9, 2020
@bogdandrutu bogdandrutu added the spec:trace Related to the specification/trace directory label Jun 12, 2020
@bogdandrutu bogdandrutu added area:sdk Related to the SDK area:semantic-conventions Related to semantic conventions labels Jun 30, 2020
@mtwo
Copy link
Member

mtwo commented Jun 30, 2020

Closing, as #380 is closed

@mtwo mtwo closed this as completed Jun 30, 2020
TuckTuckFloof pushed a commit to TuckTuckFloof/opentelemetry-specification that referenced this issue Oct 15, 2020
@kmanghat
zPages: Switching from using SpanData to custom recordable created fo…
8a02381 
…r zPages (open-telemetry#220)
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this issue Oct 21, 2024
@pyohannes @carlosalberto
Span structure for messaging scenarios (open-telemetry#220)
6ac212e 
This OTEP aims at defining consistent conventions about what spans to create for messaging scenarios, and at defining how those spans relate to each other. Instrumentors should be able to rely on a consistent set of conventions, as opposed to deducing conventions from a set of examples.

This was split from OTEP open-telemetry#192, which became too comprehensive.
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this issue Oct 23, 2024
@pyohannes
Span structure for messaging scenarios (open-telemetry#220)
66ecd12 
This OTEP aims at defining consistent conventions about what spans to create for messaging scenarios, and at defining how those spans relate to each other. Instrumentors should be able to rely on a consistent set of conventions, as opposed to deducing conventions from a set of examples.

This was split from OTEP open-telemetry#192, which became too comprehensive.
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this issue Oct 31, 2024
@pyohannes
Span structure for messaging scenarios (open-telemetry#220)
5f05a7c 
This OTEP aims at defining consistent conventions about what spans to create for messaging scenarios, and at defining how those spans relate to each other. Instrumentors should be able to rely on a consistent set of conventions, as opposed to deducing conventions from a set of examples.

This was split from OTEP open-telemetry#192, which became too comprehensive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hekike hekike

Labels
area:sdk Related to the SDK area:semantic-conventions Related to semantic conventions spec:trace Related to the specification/trace directory
Projects
None yet
Milestone
v0.6
Development

No branches or pull requests
6 participants
@carlosalberto @mtwo @bogdandrutu @hekike @jmacd @SergeyKanzhelev