Andrew Wilkins

@michaelhyatt I've transferred this to elastic/apm as (AFAICS) there's no bug with the translation of OpenTelemetry spans -- the server is translating them faithfully. It appears that API GW is...

Yes, it looks like API GW is still adding a traceparent header before both Lambdas. The producer transaction has a field `parent.id:7ade6ef5e6220237`, and the consumer transaction has `parent.id:e53f6b191e1d0281`. There are...

Possibly, I don't know. I should have said X-Ray header anyway, since there's no W3C traceparent headers involved here. The bottom line is that we're being told the producer span...

How would this be different to having cpu/memory metrics enabled? Are you suggesting that these metrics could not be disabled? Then what is the difference to not allowing cpu/memory metrics...

The server team discussed this just now, and we feel like option 2 is too fragile, since it only works if the metrics are all part of the same metric...

> Agent could simply rename metrics on the fly, for example replace . with _. While simple to change, that would make such metrics different from others that use dots...

I agree that's the best option for now. There's a new Elasticsearch enhancement request to support dotted field names at: https://github.com/elastic/elasticsearch/issues/63530

> is that all we need in order to support dots in names? @felixbarny I'm also not sure. If we have to add a `metrics.` prefix to all metrics, then...

@javanna important to note in the above: - `host.name` would be a field defined statically, ahead of time (this is an ECS field, we define it in a component template)...

> Ok with this document there is no doubt that you'll have to set subobjects: false to the root for foo and baz to both hold a value as well...