[Monitoring] APM mapping update#46244
Conversation
|
Pinging @elastic/es-core-features |
5e3400c to
29a0327
Compare
|
I assume these mappings are needed for elastic/kibana#43998? If so, I'd suggest only mapping the fields we need to index for the new UI queries/aggs introduced in that PR to work correctly. Reading through elastic/kibana#43998 that looks like |
|
Thanks, @ycombinator. I agree and have removed those two sections. |
chrisronline
left a comment
There was a problem hiding this comment.
LGTM. These seem to work fine alongside the Kibana changes
* Add acm mapping to APM for beats * Add root mapping for APM * Add sourcemap mapping to APM * Fix missing properties * Fix a second missing properties * Add request property to acm * Remove root and sourcemap per review
* Add acm mapping to APM for beats * Add root mapping for APM * Add sourcemap mapping to APM * Fix missing properties * Fix a second missing properties * Add request property to acm * Remove root and sourcemap per review Co-authored-by: Mike Place <mike.place@elastic.co>
* Add acm mapping to APM for beats * Add root mapping for APM * Add sourcemap mapping to APM * Fix missing properties * Fix a second missing properties * Add request property to acm * Remove root and sourcemap per review Co-authored-by: Mike Place <mike.place@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This creates needed mappings for additional APM metrics which were introduced by elastic/apm-server#2142