Skip to content

[APM] Jump to trace filter is invalid and return more than expected #69500

@Sayrus

Description

@Sayrus

Kibana version: 7.7.1

Elasticsearch version: 7.7.1

Server OS version: N/A

Browser version: N/A

Browser OS version: N/A

Original install method (e.g. download page, yum, from source, etc.): N/A

Describe the bug:

The current filter returns more content than expected:

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

The second part not being quoted means that depending on your configuration this can actually match any individual character in your logs.

Steps to reproduce:

  1. Open a trace in the APM section
  2. Use Jump to trace action
  3. Filter is trade.id: "XXXXXXXXXXID" OR XXXXXXXXXXID
  4. Logs returned from this filter are nearly everything in the cluster

Expected behavior:
Only logs from the filtered trace are returned

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions