An error surfaces in one place. The bug that caused it is usually somewhere else entirely.
Seer traces backward through your stack traces, breadcrumbs, spans, and logs until it finds the line that actually started the problem, not just the frame that blew up.