You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to find a URL to replace this one that we used to use to get a count of unresolved errors/events. The first thing I tried is fiddling the statsPeriod knob, since that's what seems to limit the events by time. Doing so gives me an infinite spinner in the UI and an Uncaught TypeError: Cannot read property '' of undefined in the console, pointing to groupChart.jsx. The docstring and code for project_group_index.get seem to indicate that '' should be considered a valid value.
Whether this is the best way to find the count of unresolved events is another question.
The text was updated successfully, but these errors were encountered:
You haven't actually (realistically) been able to get a count of unresolved events, at least not the total number. Everything else should effectively be the same.
Can you clarify what the data you're looking for is?
@dcramer Ideally I'd like the total number of unresolved events, as well as the total number of resolved events. Sentry is one of about a dozen queues we monitor weekly with this type of data (e.g.), and it's the only one we've had a hard time determining these counts for.
You haven't actually (realistically) been able to get a count of unresolved events, at least not the total number.
Right. We were hacking it with cursor paging over an "all time" query. A more straightforward solution would be welcome. :-)
I'm trying to find a URL to replace this one that we used to use to get a count of unresolved errors/events. The first thing I tried is fiddling the
statsPeriod
knob, since that's what seems to limit the events by time. Doing so gives me an infinite spinner in the UI and anUncaught TypeError: Cannot read property '' of undefined
in the console, pointing to groupChart.jsx. The docstring and code forproject_group_index.get
seem to indicate that '' should be considered a valid value.Whether this is the best way to find the count of unresolved events is another question.
The text was updated successfully, but these errors were encountered: