[APM] Diplay logs only matching trace.id query

[kpatticha]

Summary

closes: #126342

related

#85859 (comment)

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[dgieselaar]

@kpatticha I assumed the wider matching was intentional, maybe to also display non-ECS compatible log messages. It's also how we link to the Logs UI. Did we run this by @alex-fedotyev? I think he is the in-house APM logs expert 😄

[gbamparop]

Doesn't it make sense to also change the link in

kibana/x-pack/plugins/apm/public/components/shared/transaction_action_menu/sections.ts

Line 171 in d16a4d8

filter: `trace.id:"${transaction.trace.id}" OR "${transaction.trace.id}"`,

?

[kpatticha]

@kpatticha I assumed the wider matching was intentional, maybe to also display non-ECS compatible log messages. It's also how we link to the Logs UI. Did we run this by @alex-fedotyev? I think he is the in-house APM logs expert 😄

No Cyrille opened a bug for this. .
Oliver also pointed this in his PR when he worked on adding logs tab but couldn't find if it was intertional. My understading is we tried to follow the same as here query .

@alex-fedotyev what do you think about this change?

[sorenlouv]

I assumed the wider matching was intentional, maybe to also display non-ECS compatible log messages

I originally suggested the wider matching in #79995. I can't remember why and cannot find any discussion of this so I suggest to go ahead with this change (as long as @alex-fedotyev don't have any objections).

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 78d8e01
• Storybooks Preview

Failed CI Steps

• APM Cypress Tests

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
apm	3.0MB	3.0MB	+42.0B

History

• 💔 Build #61716 failed 1585430
• 💚 Build #59779 succeeded a0dabcd

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.4

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation