Clarifications to S3 tracing spec

[trentm]

@AlexanderWert Here are some clarifications to the S3 tracing spec. I assume some of these were copypasta from the DynamoDB section. Some removal of trailing whitespace is included in this diff (sorry about that), so this will be a slightly cleaner diff: https://github.com/elastic/apm/pull/451/files?w=1

Rendered: https://github.com/elastic/apm/blob/trentm/s3-copypasta/specs/agents/tracing-instrumentation-db.md#aws-s3

(I have some non-trivial Qs about the spec but I'll ask those separately.)

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Pull request #451 updated

• Start Time: 2021-06-16T16:44:05.365+0000

• Duration: 3 min 51 sec

• Commit: dc52a84

Trends 🧪

[russcam]

LGTM, thanks @trentm 👍

[AlexanderWert]

Thanks @trentm.

In general LGTM, maybe let's wait with merging until we decided what to do with context.db for S3.

[trentm]

maybe let's wait with merging until we decided what to do with context.db for S3.

For others following, Alexander and I discussed separately and decided to merge this and I'll have another PR later with more substantive changes (like proposing dropping span.context.db.* for S3) after some more discussion.

[From the process doc]

1. The PR can be merged by the author of the PR
   One business day before merging, there should be a last call for objections.
   This last call is not mandatory and is a good candidate for being automated in the future.

I don't think this PR is contentious. Also it doesn't appear that the Go, Python, or Ruby agents (the one who've currently implemented S3 instrumentation) add span.context.db.* for S3 spans, so the change in the spec here doesn't affect current implementations.