-
Notifications
You must be signed in to change notification settings - Fork 107
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 S3 Bucket and Object Key to S3 instrumentation (OTel) #788
Conversation
@AlexanderWert, others: Do you think we should consider also adding |
Good point @trentm! Yes, I think that makes sense. |
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.
LGTM (once #788 (comment) is merged).
Co-authored-by: Trent Mick <trent.mick@elastic.co>
I'd prefer to have it separately. I'll create a spec issue and one for the agents that may implement it. |
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.
LGTM (just added a minor syntactical proposal to make it consistent)
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
Updated the AWS S3 Spec by adding Bucket and Object Key into OpenTelemetry attributes (otel)
sanitize_field_names
)CODEOWNERS
)To auto-merge the PR, add
/
schedule YYYY-MM-DD
to the PR description.Closes: #760