Custom tags not added to Perfromance Issues

[landenai]

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/nextjs

SDK Version

8.37.1

Framework Version

Next 15.0.1

Link to Sentry event

https://demo.sentry.io/issues/6396022267/?project=4508968158429184&query=&referrer=issue-stream&sort=date&stream_index=0

Reproduction Example/SDK Setup

I add a custom tag within a server action before a query is made that triggers a performance issue. When testing locally, I see the tag on the perfromance issue in Sentry. When testing on my vercel deployment, I do not see the tag. Here is how I add the tag

Note: Ive already added console log statements and seen that se has a value.

Steps to Reproduce

1. Add tag to current scope before query that triggers an N + 1 perfromance issue is made
2. Trigger issue in Vercel, observe in Sentry

Expected Result

Tag is observable on performance issue in Sentry

Actual Result

Tag is not added to performance issue in Sentry

[AbhiPrasad]

Hey @landenai - if you capture an error, do you get the custom tag applied?

Could you also try running Sentry.setTag directly?

[landenai]

Yes, different function but same server action. We capture an error and can see the tag in Sentry. I just tried Sentry.setTag with the same result

[lforst]

Performance events are created on the server from transactions (and spans) and transactions don't have tags so I think this is moot (?).

[landenai]

Are we not suppose to be able to add tags to perfromance events? I've seen performance events with tags successfully added but maybe this wasn't intended functionality

[AbhiPrasad]

Transactions do have tags, and the performance issue should be inheriting from the transaction. The fact that it works locally but not on vercel is the red flag for me.

I suspect what is happening is that on Vercel when we finish the transaction we aren’t in the right context anymore (outside of request) so we grab stuff from the wrong scope. Therefore the setTag call no longer applies.

@landenai One thing you could do to double check this is to do Sentry.getIsolationScope().setTag

[landenai]

@AbhiPrasad Sorry for the delay here, just tested getIsoloationScope and same result as expected