Clarify that stdout exporter format is unspecified#4418
Clarify that stdout exporter format is unspecified#4418reyang merged 13 commits intoopen-telemetry:mainfrom
Conversation
|
Need a changelog entry. |
|
Overall LGTM. Probably we should change the warning to something along the lines of "Review the file exporter status, in order to verify it is production ready" etc (otherwise this will get eventually outdated). |
jsuereth
left a comment
There was a problem hiding this comment.
I have concerns about what message we send with this and the recent blog post here: https://opentelemetry.io/blog/2024/collecting-otel-compliant-java-logs-from-files/
I think if we are going to recommend FileExporter, we should make sure SOMETHING can support that blog article such that we can update its examples.
It looks like the blog post already showcases the OTLP/JSON FileExporter unless I missed something. |
As clarified by Robert here, Blog already suggests using the FileExporter, which is also what this PR suggests. |
February 2025 Release. - Deprecate `exception.escaped` attribute, add link to in-development semantic-conventions on how to record errors across signals. ([open-telemetry#4368](open-telemetry#4368)) - Define randomness value requirements for W3C Trace Context Level 2. ([open-telemetry#4162](open-telemetry#4162)) - Define how SDK implements `Logger.Enabled`. ([open-telemetry#4381](open-telemetry#4381)) - Logs API should have functionality for reusing Standard Attributes. ([open-telemetry#4373](open-telemetry#4373)) - Define syntax for escaping declarative configuration environment variable references. ([open-telemetry#4375](open-telemetry#4375)) - Resolve various declarative config TODOs. ([open-telemetry#4394](open-telemetry#4394))
For your consideration. Related to the confusion here: open-telemetry#4420 (comment)
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
…lper (open-telemetry#4421) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
February 2025 Release. - Deprecate `exception.escaped` attribute, add link to in-development semantic-conventions on how to record errors across signals. ([open-telemetry#4368](open-telemetry#4368)) - Define randomness value requirements for W3C Trace Context Level 2. ([open-telemetry#4162](open-telemetry#4162)) - Define how SDK implements `Logger.Enabled`. ([open-telemetry#4381](open-telemetry#4381)) - Logs API should have functionality for reusing Standard Attributes. ([open-telemetry#4373](open-telemetry#4373)) - Define syntax for escaping declarative configuration environment variable references. ([open-telemetry#4375](open-telemetry#4375)) - Resolve various declarative config TODOs. ([open-telemetry#4394](open-telemetry#4394))
Done! |
|
@jsuereth Please check #4418 (comment) and let me know if any change required. |
Merging, if there is additional feedback from @jsuereth, please send a follow up PR. |
March 2025 Release. ## v1.43.0 (2025-03-11) ### Traces - Clarify STDOUT exporter format is unspecified. ([#4418](#4418)) ### Metrics - Clarify STDOUT exporter format is unspecified. ([#4418](#4418)) ### Logs - Clarify that it is allowed to directly use Logs API. ([#4438](#4438)) - Clarify STDOUT exporter format is unspecified. ([#4418](#4418)) ### Supplementary Guidelines - Add Advanced Processing to Logs Supplementary Guidelines. ([#4407](#4407)) --------- Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
Continuing https://github.com/open-telemetry/opentelemetry-specification/pull/3935/files which got stale and closed.
@MrAlias is the original author of the above PR.
If the wording is agreed, I'll extend to all signals and update changelog.Done!