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

Span.Kind.LOAD_BALANCER (PROXY/SIDECAR) #51

Open
bogdandrutu opened this issue Apr 17, 2019 · 4 comments
Open

Span.Kind.LOAD_BALANCER (PROXY/SIDECAR) #51

bogdandrutu opened this issue Apr 17, 2019 · 4 comments
Labels
area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
Milestone
Future

Comments

@bogdandrutu
Copy link
Member

In some cases some of the sidecar/load_balancer implementations will generate only one span between a client and a server spans. Do we want to have a kind that describes this case so that backends will know this is an rpc like client -> proxie -> server?
@SergeyKanzhelev
Copy link
Member

I think we can defer this to later

@bogdandrutu
Copy link
Member Author

Sure, but want to track it.

@bogdandrutu bogdandrutu transferred this issue from open-telemetry/opentelemetry-java May 31, 2019
@SergeyKanzhelev SergeyKanzhelev added this to the API revision: 07-2019 milestone Jun 3, 2019
@iredelmeier iredelmeier added the area:semantic-conventions Related to semantic conventions label Jul 30, 2019
@SergeyKanzhelev SergeyKanzhelev modified the milestones: API revision: 07-2019, Future Sep 27, 2019
@jmacd
Copy link
Contributor

jmacd commented Dec 4, 2019

See https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/api-tracing.md#spankind for the current specification.

@jmacd
Copy link
Contributor

jmacd commented Dec 4, 2019

There was unresolved discussion in #337 about how to handle pass-through proxies.

This was referenced Dec 4, 2019
Open
Closed
@Oberon00 Oberon00 mentioned this issue Jan 20, 2020
Open
@fbogsany fbogsany mentioned this issue Feb 28, 2020
Merged
@bogdandrutu bogdandrutu added the spec:trace Related to the specification/trace directory label Jun 12, 2020
@carlosalberto carlosalberto added the release:after-ga Not required before GA release, and not going to work on before GA label Jul 2, 2020
TuckTuckFloof pushed a commit to TuckTuckFloof/opentelemetry-specification that referenced this issue Oct 15, 2020
@eyakimov-bbg
Minor typos/fixes (open-telemetry#51)
edf171e
rockb1017 pushed a commit to rockb1017/opentelemetry-specification that referenced this issue Nov 18, 2021
@flands
Merge pull request open-telemetry#51 from signalfx/flands/freeze2
30806c6 
Clarify configuration env vars
@arielvalentin arielvalentin mentioned this issue Feb 22, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
Projects
None yet
Milestone
Future
Development

No branches or pull requests
5 participants
@carlosalberto @bogdandrutu @iredelmeier @jmacd @SergeyKanzhelev