Issues are being tracked with the wrong environment

[ruby magnet]

I have a React Vite sentry project that is using the sha as the release name and three environments: deploy-preview, staging, and production.

We use the vite plugin and the react integration, set the release and deploy info via the vite plugin and allow it to inject that info into the build.

I'm seeing e2e tests claiming to run against our staging url with an environment of "production" which from looking at how our CI is set up should not be happening.

I would expect my environments to match and for me to be able to differentiate the different deployments of the same commit sha.

[low tide]

Hi, enviroment "production" is set as a default during event ingestion on the sentry backend, if no explicit environment was passed in via Sentry.init. I'd suggest checking which environment is being sent in your staging setup. For example, you can log our error events in beforeSend