mirror of
https://github.com/elastic/kibana.git
synced 2025-04-25 02:09:32 -04:00
When we link to Logs UI from a trace summary or a transaction flyout, we set the filter parameter to trace.id:"${traceId}". However, we shouldn't make the presence of the trace.id field a hard requirement. Not all users have set up their pipeline to parse the trace id from a log line, but the trace id still might be present in the message. Widen the filter when linking to trace.id:"${traceId}" OR ${traceId} to accommodate this situation. Fixes #45346.
This commit is contained in:
parent
17235feb0b
commit
13e30097cb
1 changed files with 4 additions and 1 deletions
|
@ -118,7 +118,10 @@ export const TransactionActionMenu: FunctionComponent<Props> = (
|
||||||
),
|
),
|
||||||
condition: true,
|
condition: true,
|
||||||
path: `/link-to/logs`,
|
path: `/link-to/logs`,
|
||||||
query: { time, filter: `trace.id:${transaction.trace.id}` }
|
query: {
|
||||||
|
time,
|
||||||
|
filter: `trace.id:"${transaction.trace.id}" OR ${transaction.trace.id}`
|
||||||
|
}
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
icon: 'infraApp',
|
icon: 'infraApp',
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue