Skip to content

Commit d18137b

Browse files
authored
chore(issue-details): Add num_exceptions to issue details viewed analytics event (#99436)
gives more insight into chained exceptions
1 parent 464c28b commit d18137b

File tree

1 file changed

+5
-0
lines changed
  • static/app/components/events/interfaces/crashContent/exception

1 file changed

+5
-0
lines changed

static/app/components/events/interfaces/crashContent/exception/content.tsx

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ import type {Event, ExceptionType, ExceptionValue} from 'sentry/types/event';
1717
import type {Project} from 'sentry/types/project';
1818
import {StackType} from 'sentry/types/stacktrace';
1919
import {defined} from 'sentry/utils';
20+
import useRouteAnalyticsParams from 'sentry/utils/routeAnalytics/useRouteAnalyticsParams';
2021
import useProjects from 'sentry/utils/useProjects';
2122
import {SectionKey} from 'sentry/views/issueDetails/streamline/context';
2223
import {
@@ -256,6 +257,10 @@ export function Content({
256257

257258
const isSampleError = useIsSampleEvent();
258259

260+
useRouteAnalyticsParams({
261+
num_exceptions: values?.length ?? 0,
262+
});
263+
259264
// Organization context may be unavailable for the shared event view, so we
260265
// avoid using the `useOrganization` hook here and directly useContext
261266
// instead.

0 commit comments

Comments
 (0)