Alerts without escaped exceptions

[harm-matthias-harms]

How does the community typically handle alerts for exceptions that occur in any of the child spans and are not rescued within the parent spans?

Some of my current thoughts:

• exception.escaped is deprecated and not implemented in most SDKs.
• Many applications record spans at a fine-grained level, which means most exceptions are not handled in the same span where they occur, but rather in one of the parent spans.
• Using signoz_traces.distributed_signoz_index_v3 is challenging because the stack trace is stored in the event of a failed child span, while the searched parent should be the top-most parent within the same service name of the trace. This makes it difficult to construct a query that reliably captures all cases.

[srikanthccv]

Can you give an example for your setup, 1. where does the exception happen? 2. where is captured? 3. Where is it handled?

[harm-matthias-harms]

This existing issue describes the problem too. Exceptions in Ruby are sometimes used for control flow.

open-telemetry/opentelemetry-ruby-contrib#1459