topic Did the filtering on Exception message stop working in Distributed Tracing? in Dashboarding

Did the filtering on Exception message stop working in Distributed Tracing?

rikvangeffen — Wed, 29 Oct 2025 07:43:05 GMT

Hi there,

Per today I noticed that filtering on a != or "not in" way on "Exception message" does not work anymore in distributed tracing, for example:

Service = "SERVICE_NAME" AND "Request status" = Failure AND "Exception message" != "ERROR_MESSAGE

used to give responses, but now it can't find any requests, and under the hood it gives me this error:

"errorType": "PARSE_ERROR",
"errorMessage": "`|` isn't allowed here. Please check the autocomplete suggestions before the error for alternative options.",

Re: Did the filtering on Exception message stop working in Distributed Tracing?

MaximilianoML — Tue, 28 Oct 2025 11:25:32 GMT

Hello @rikvangeffen !
Let me try to have a better understanding, where are you trying to make this search?

Maximiliano Lopes

Re: Did the filtering on Exception message stop working in Distributed Tracing?

rikvangeffen — Tue, 28 Oct 2025 11:30:18 GMT

Hi Maximiliano, actually a simple query for removing certain error messages so I can focus on others.

To give you an example:

This works: "Exception message" = "Location not found*"
But this doesn't not: "Exception message" != "Location not found*"

Re: Did the filtering on Exception message stop working in Distributed Tracing?

MaximilianoML — Tue, 28 Oct 2025 12:00:54 GMT

Alright, thanks for sharing.
So, according to the docs I saw, you must need this type of filtering:
DQL | NOT Matcher

I can't really tell why that doesn't work anymore, but I tried with this example above and worked fine, let me know when you try.

Maximiliano Lopes

Re: Did the filtering on Exception message stop working in Distributed Tracing?

siavash1996 — Tue, 28 Oct 2025 15:53:22 GMT

I put in a ticket with Support for a similar issue. We could no longer filter using request attributes on the new Distributed Tracing app. I got this reply:

It seems likely that we have a regression in our latest release of the Distributed Tracing Platform App, as there are now multiple Customer's reporting the same issue. I have escalated this problem to the Development team for further review. In the meantime, please use the Distributed Traces Classic App as best as possible for a workaround.

So we'll just have to wait for a SaaS hotfix.