Bug in the TraceView. probably regression Exceptions started to be shown out of their group and order.

[amiranvarov]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

7.116.0

Framework Version

express@^4.18.1

Link to Sentry event

https://amir-anvarov.sentry.io/share/issue/92e66980e5844d5baa96348c1a5247cd/

SDK Setup

Sentry.init({
		serverName: name,
		dsn: dsn,
		environment: env.node_env,
		enabled: true,
		debug: debug,
		integrations: [
			// enable HTTP calls tracing
			new Sentry.Integrations.Http({ tracing: true }),
			// enable Express.js middleware tracing
			new Tracing.Integrations.Express({ app }),
			new ProfilingIntegration(),
			...integrations,
		],
		beforeSend(event, hint) {
			const error = hint.originalException as Error;
			if (error?.message?.match(/database unavailable/i)) {
				event.fingerprint = ["database-unavailable"];
			}

			// Modify or drop the event here
			if (event.user) {
				// Don't send user's email address
				event.user.email = undefined;
			}

			return event;
		},

		// Called for transaction events
		beforeSendTransaction(event) {
			// Modify or drop the event here
			if (event.transaction === "/unimportant/route") {
				// Don't send the event to Sentry
				return null;
			}
			return event;
		},
		beforeBreadcrumb(breadcrumb, hint) {
			// Check if the breadcrumb has sensitive data like user email
			if (breadcrumb.data?.["user"]?.email) {
				// Remove the user email from the breadcrumb
				// Remove the user email from the breadcrumb
				breadcrumb.data["user"].email = undefined;
			}
			return breadcrumb;
		},
		includeLocalVariables: true,
		attachStacktrace: true,
		// Set tracesSampleRate to 1.0 to capture 100%
		// of transactions for performance monitoring.
		// We recommend adjusting this value in production
		tracesSampleRate: 1.0,
	});

Steps to Reproduce

Would be hard to give me instructions how to reproduce. You should set up microservice architecture app.

I think it would be easier if I share my screen with parts of my code with you as i can't expose my private repo itself.

before you tell me to look at my code search for issues there, i'll tell you I did it for the past 5 hours, i have been going trough my code to see if i broke something. i reverted back to commit when my sentry Trace view was perfectly showing me in the timeline where exactly exception was captured, in which of my microservice, after which span and etc. But even after i checked out that commit when sentry and my code was aligned perfectly, i'm still having an issue with how TraceView is displaying exceptions positon on my trace timeline. I am very confident that problem is not in my code.

Out of nowhere, Sentry right now is showing captured exceptions out of order and not correctly. I suspect maybe there was some issue with latest realese of traceview, on Sentry side.

Expected Result

Exceptions are being displayed in the order, in related group, just like it was a weegk ago

Actual Result

Exceptions started to be displayed out of order, out of the group

[mydea]

Hey,

to clarify, where did you encounter problems? What version worked, and what version stopped working for you?

[amiranvarov]

hey, just described it in your Dicsord. Will copy and paste the screenshot:

[JonasBa]

@amiranvarov it would be helpful if you can send us a link to a trace where the events are ordered correctly vs when they are not as we need to look at the data to figure out what timestamps are reported.

It would be very weird if profiling had any impact on this as it does not change when issue timestamps are changed. Did you change anything around the docker image or sentry SDK with the change to downgrade the profiling SDK? In addition, could you provide us with that docker logfile so that we can see why it crashed?