Breadcrumbs are not indexed, please add a breadcrumb data type with some basic info, like previous error

[JohnDuncanScott]

Problem Statement

Say a Metric is being sent via captureMessage. I would like to know the latest error that happened in the breadcrumb trail for a set of metrics.

Currently I would have to open each issue, scan the breadcrumbs and find the last error. This takes a long time and is tedious.

It would be super nice if there was someway of querying what the last error was in a breadcrumb trail.

For example, like with stacktrace, maybe there could be a breadcrumb.last_error field or something like that? Essentially something that could be shown as a column and queried on without having to dig into each issue.

Hope that makes sense.

Solution Brainstorm

Add a new datatype, like stacktrace, that has various info on it. For a start, it could be:
breadcrumb.last_error (plus timestamp)
breadcrumb.last_info (plus timestamp)
breadcrumb.last_warning (plus timestamp)

I think this would make large scale analyses easier.

[getsentry-release]

Routing to @getsentry/workflow for triage. ⏲️

[Dhrumil-Sentry]

Hi @JohnDuncanScott Can you try sending this metric as a tag for an issue? Then each event could be grouped into the same issue and you can use Discover to search for the tag easily

[JohnDuncanScott]

Sure, this could be fixed with tags in some cases, but it would still give you a group that then needs searching through. You could argue the same about why stack traces exist as a separate set of indexed columns - you could create a stacktrace tag yourself but it's built into Sentry. Most of these types of issues can be fixed by adding a variety of tags. I just think having some breadcrumb info that's already indexed for you, without needing to add lots of extra tags, would be useful. This is especially useful when errors sometimes get suppressed from Sentry due to capping, etc.. Does that make sense?

[Dhrumil-Sentry]

Thanks for the response, This is something we will add to the backlog but are unlikely to prioritize in the new 2 quarters.