open-telemetry / open-telemetry/opentelemetry-python
Stabilize Logs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
After confirming all of the following have been taken care of, I think we can stabilized logs. Got these from https://github.com/open-telemetry/opentelemetry-specification/issues/2911
- Confirm LogRecord emit does not overwrite unspecified timestamp https://github.com/open-telemetry/opentelemetry-specification/issues/3386
- Drop log API include_trace_context parameter https://github.com/open-telemetry/opentelemetry-specification/pull/3397
- Clarify how ObservedTimestamp field is set if unspecified #3385
- https://github.com/open-telemetry/opentelemetry-specification/pull/3383
Is your feature request related to a problem?
Leaving Logs unstable enabled breaking changes like https://github.com/open-telemetry/opentelemetry-python/pull/2943
Describe the solution you'd like
With the logging spec stable, we should confirm we have everything we need and stabilize logs as soon as possible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked OpenTelemetry specification issues and pull requests, then inspect the referenced opentelemetry-python pull request #2943. Identify any remaining requirements for stable Logs and confirm that the implementation is ready to remove its unstable status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100