You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are you trying to achieve?
The appendix sections of the Data Model document are currently tied up with the stability of the Data Model document itself. This isn't ideal, because these appendices are meant to be informational and not canonical representations of these format mappings. If the owner of that log format, for example a vendor maintaining an exporter, needed to change something about the format mapping they shouldn't be concerned with how it affects the overall stability of the data model document.
I'd like to propose that these examples be moved into a separate document, where it's clarified that the document is not a spec and makes no stability guarantees. The main Data Model document should likely link out to this document, as the examples are still valuable and should be easy to find.
Additional context.
This was brought up in the Dec 3 and Feb 8 Logging SIGs, and seemed to be well agreed upon. I offered to make the PR that made the change.
The text was updated successfully, but these errors were encountered:
Fixes#3206
## Changes
This PR moves Data Model Appendix A and Appendix B to a separate
document, disentangling these appendices from the stability of the Data
Model document itself.
---------
Co-authored-by: Tigran Najaryan <[email protected]>
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 31, 2024
Fixesopen-telemetry#3206
## Changes
This PR moves Data Model Appendix A and Appendix B to a separate
document, disentangling these appendices from the stability of the Data
Model document itself.
---------
Co-authored-by: Tigran Najaryan <[email protected]>
What are you trying to achieve?
The appendix sections of the Data Model document are currently tied up with the stability of the Data Model document itself. This isn't ideal, because these appendices are meant to be informational and not canonical representations of these format mappings. If the owner of that log format, for example a vendor maintaining an exporter, needed to change something about the format mapping they shouldn't be concerned with how it affects the overall stability of the data model document.
I'd like to propose that these examples be moved into a separate document, where it's clarified that the document is not a spec and makes no stability guarantees. The main Data Model document should likely link out to this document, as the examples are still valuable and should be easy to find.
Additional context.
This was brought up in the Dec 3 and Feb 8 Logging SIGs, and seemed to be well agreed upon. I offered to make the PR that made the change.
The text was updated successfully, but these errors were encountered: