No-op span ID generation #159

New issue

Copy link

New issue

Copy link

Closed

Closed

No-op span ID generation#159

Copy link

Assignees

Labels

apiAffects the API package.Affects the API package.discussionIssue or PR that needs/is extended discussion.Issue or PR that needs/is extended discussion.release:required-for-gaTo be resolved before GA releaseTo be resolved before GA releasetracing

Description

reyang

opened on Sep 20, 2019

Issue body actions

1. If the span is not sampled, we shouldn't create a real span.
2. If the span is sampled, and there is just the API package (not the SDK package), the outgoing span (SpanKind = Server) should generate a new span id (but not a new trace id) in order to be compliant with W3C TraceContext. All the in-process spans should be dummy spans (zero span id).
3. If the span is sampled, and there is SDK package, everything should just work, and compliant with W3C TraceContext.
4. Integrations should not try to tell if SDK exists or not, integrations should not try to tell if SDK exists or not and perform special operations.

Metadata

Metadata

Assignees

• 
  codeboten

Labels

apiAffects the API package.Affects the API package.discussionIssue or PR that needs/is extended discussion.Issue or PR that needs/is extended discussion.release:required-for-gaTo be resolved before GA releaseTo be resolved before GA releasetracing

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions