Deprecating Span Events feedback

Open
#3,312 11 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Domain
documentation

Research direction

Read the linked deprecating-span-events blog post first. Provide feedback on which compatibility aspects matter most, such as span event visibility in trace views, inclusion in the same OTLP export payload as parent spans, or other tooling-dependent behavior; done means documenting relevant use cases in this issue.

Written by the indexing model from the issue text.

Description

Please share your feedback for https://opentelemetry.io/blog/2026/deprecating-span-events/.

We are especially interested in which compatibility aspects matter most to you, for example, whether you rely on seeing events directly on spans in trace views, on having events included in the same OTLP export payload as their parent spans, or on other behaviors your current tooling depends on.

Thank you!

Dominant language
Python
Stars
1.2k
Forks
326
Avg merge
1d 12h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-telemetry/community

All issues in open-telemetry/community

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.