Populate environment for Sentry
The Sentry integration sends issues with the environment set to "default", which makes it tough to do things like filtering for alerts.
Would be great if "development", "preview", and "production" were used based on the deployment.
9 Replies
I also can not figure out for the life of me the difference between the environment of a Sentry issue and the environment tag of a Sentry issue. I've been messing around with alert filters and I'm not even sure Sentry knows the difference.
@nipunn
sounds like a great idea to set environment to one of development/preview/production. It matches sentry's concept of environment here https://docs.sentry.io/product/sentry-basics/concepts/environments/
Environments
Learn more about how environments can help you better filter issues, releases, and user feedback in the Issue Details page on sentry.io.
Noted!
@erquhart this might be the environment that is currently "default" (what we're calling our V8 Isolate Convex JS runtime) vs "node," so this change Nipunn is proposing sounds good
ah hadn't considered that. That might still be helpful to keep if that's the case, maybe as a "runtime" tag? At any rate, agree that Nippun's proposal would work well.
transversely, you could also leave "environment" as is (assuming it does return "node" for node functions) and add a new "deployment" tag with the deployment info.
yeah - I think changing "environment" to "runtime" and rebranding "environment" to match sentry's sense of production/preview/development feels like a good change to me
Sup @erquhart - this just shipped!
We also shipped adding request_id as a tag - so you can cross correlate with the logs page. sshader and me have been working on it.
Nice!! Thanks for the heads up!