Andrew Wilkins

> Is there a corresponding UI issue for this? Doesn't look like it. We had (have?) one for `timestamp.us`, but that turned out to be too difficult to target 8.0....

@Mpdreamz not a bad idea, but there are some complications: 1. Transactions and spans both end up in the same index, so we'll have `transaction.duration.us` and `span.duration.us` in the same...

I'm moving this out of 8.0, as we need to take a broader look at backwards compatibility of field changes like this.

One option would be to change our docker image building to build the apm-server binary on the host, and copy it into the image. Then all the usual `go.mod` functionality...

> either reinstate fields This would not be unreasonable, as we're considering pass-through of arbitrary OpenTelemetry attributes. To do that, we'll flatten all fields (so `foo.bar.baz` is written as a...

@simitt do they need to variable? If someone wanted to do processing based on the apm-server instance, they could use `observer.hostname` in their ingest pipeline. What I had in mind...

@dvisztempacct > Right now I'm using metadata to transit the traceparent ID, but it's worrying to me that this won't be compatible with other agents. The Go agent is also...

@dvisztempacct no, you're not misunderstanding; I just don't know how to JavaScript properly :wink: Just wanted to show that what you had intended to do will work with the Go...

@sarabu07 which specific database/sql driver package are you using?

> However, it seems that context is only being set if the request body is not nil. > That seems a bit weird. @axw do you know the reason for...