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.

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

add note about reporting dropped attributes/events/links #1699

Merged
merged 6 commits into from
May 19, 2021

Conversation

codeboten
Copy link
Contributor

Fixes #1698

Changes

Clarify that dropped counts should be reported from the SDK. Would love feedback from reviewers on whether or not this change should include a change to the matrix.

Related issues #1656

@codeboten codeboten requested review from a team as code owners May 13, 2021 22:48
@@ -356,6 +356,10 @@ There SHOULD be a log emitted to indicate to the user that an attribute, event,
or link was discarded due to such a limit. To prevent excessive logging, the log
should not be emitted once per span, or per discarded attribute, event, or links.

Counts for attributes, events and links dropped due to collection limits MUST be reported
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this MUST is too much, as it depends on the protocol. What we should say is that the counts MUST be available for exporters. I think this would best fit in the "readable span" wording, somewhere around https://github.com/open-telemetry/opentelemetry-specification/pull/1699/files#diff-ace73543d690260e873d774428419c23895283b6c31177d405816b154d1f5aa0R91

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Oberon00, I updated the note, PTAL.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be best to move this wording to the "readable span" definition, somewhere around line 91, as this will probably be the part where this wording has to be implemented. But semantically, the change looks good to me!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codeboten Could you update this part according to @Oberon00 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

Copy link
Member

@Oberon00 Oberon00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but see #1699 (comment)

@carlosalberto carlosalberto merged commit 9367663 into open-telemetry:main May 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No mention of dropped attributes/events/links counts in SDK spec
4 participants