-
Notifications
You must be signed in to change notification settings - Fork 896
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.
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
Clarify that STDOUT exporter format is unspecified #3935
Conversation
4adb602
to
b22f796
Compare
This approach has not been decided on: #3565 |
@MrAlias Do you plan to re-open this, and add this language to the spec wording for stdout? This looks a good addition! |
👍 |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
@@ -10,6 +10,12 @@ linkTitle: Stdout | |||
Exporter](../sdk.md#logrecordexporter) which outputs the logs to | |||
stdout/console. | |||
|
|||
The output format of the exporter is unspecified. The exporter SHOULD be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we actually specify some requirements for the format (e.g. that it is not performance optimized) I wonder if it is better to say:
The output format of the exporter is unspecified. The exporter SHOULD be | |
The output format of the exporter is implementation-dependant. The exporter SHOULD be |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
Resolve #3565
Changes
The output format of the STDOUT exporter is unique to each OpenTelemetry language implementation. Reflect this in the specification and add normative requirements and suggestions for language implementations to document the exporter appropriately.