Strange behaviour with APM and negation filters

Jeremy_Cohen_Solal
Thu, 16 Mar 2023 08:59:08 +0000
APM

Kibana version: tested on 7.17.8 and latest (8) locally

Elasticsearch version: same

APM Server version: same

APM Agent language and version: python

Browser version: chrome

Original install method (e.g. download page, yum, deb, from source, etc.) and version: all

Fresh install or upgraded from other version? both

Is there anything special in your setup? nothing special

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant): In APM view, I want to filter all transactions which are not POST. Using this doc with a NOT keyword... it does not filter correctly transactions... and when I click on a transaction.. I get a error message "The selected trace can not be found"

Steps to reproduce:

1. go to a service in APM

2. filter with NOT http.request.method:POST

3. look at filtered transaction list > we can still see POST transactions

4. click on a POST transaction which shouldn't be displayed

5. error message (stack trace not found)

6. if you remove the NOT in this transaction page, it seems to bring back to a standard behaviour

Errors in browser console (if relevant): ras

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

5 posts - 3 participants