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

Define what constitutes breaking change for Logs #2884

Closed
jsuereth opened this issue Oct 17, 2022 · 1 comment
Closed

Define what constitutes breaking change for Logs #2884

jsuereth opened this issue Oct 17, 2022 · 1 comment
Assignees
@jsuereth
Labels
area:semantic-conventions Related to semantic conventions [label deprecated] triaged-needmoreinfo [label deprecated] The issue is triaged - the OTel community needs more information to decide spec:logs Related to the specification/logs directory

Comments

@jsuereth
Copy link
Contributor

Similar to #2864 we need to define / propose what changes to Logs are considered breaking and what are allowable.
@jsuereth jsuereth added area:semantic-conventions Related to semantic conventions spec:logs Related to the specification/logs directory labels Oct 17, 2022
@jsuereth jsuereth self-assigned this Oct 17, 2022
@arminru arminru removed their assignment Oct 24, 2022
@carlosalberto carlosalberto added the [label deprecated] triaged-needmoreinfo [label deprecated] The issue is triaged - the OTel community needs more information to decide label Oct 24, 2022
@jsuereth
Copy link
Contributor Author

This was fixed in #3225

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jsuereth jsuereth

Labels
area:semantic-conventions Related to semantic conventions [label deprecated] triaged-needmoreinfo [label deprecated] The issue is triaged - the OTel community needs more information to decide spec:logs Related to the specification/logs directory
Projects
Semantic Conventions + Instrumentation Stability WG
Status: Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jsuereth @carlosalberto @arminru