[BUG]: Error tracking default grouping is taking gem frames into account

[agrobbin]

Tracer Version(s)

2.21.0

Ruby Version(s)

ruby 3.4.6 (2025-09-16 revision dbd83256b1) +PRISM

Relevent Library and Version(s)

pg 1.6.2

Bug Report

We had 2 instances of PG statement timeouts in different areas of the application. In one case, that scenario is unfortunate but expected (it is gracefully retried in the background) and was ignored in DD Error Tracking, however in another area it is entirely unexpected and was a sign of an issue to be investigated.

Unfortunately, the error fingerprint of both exceptions was grouped together, and according to the Error Tracking grouping explanation, the reason it was grouped together was because of the actual datadog gem tracing:

This seems like a surprising experience, with Datadog tracing actually changing the grouping logic of errors.

Reproduction Code

No response

Configuration Block

No response

Error Logs

No response

Operating System

No response

How does Datadog help you?

No response

[ivoanjo]

Hey! Thanks a lot of the report, and sorry for the issue.

Can I ask that you report this via the support request link? Since this may need some work from both dd-trace-rb and some tweaks on the error tracking part, we should be able to better communicate and escalate via that route.

[agrobbin]

@ivoanjo sure thing! I've opened request #2268925 with the same info. Happy to provide additional details as necessary in that system.

[ivoanjo]

Perfect, I can see it on our support board, thank you!

[marcovaccari]

Hello 👋 Do you have some updates on this issue? As we are facing the same

[ivoanjo]

Hey @marcovaccari! Unfortunately the fix will need some work on the backend side and will take some time 😓

I've left a note on the internal ticket to +1 on your behalf on this.