Sentry environment issue
Unanswered
Tonkinese posted this in #help-forum
TonkineseOP
We are using the next.js app router for our application.
Errors are being triggered and sent to sentry correctly, however, the environment name, where the issue is triggered is incorrect.
If I manually capture an exception on a production or QA url, the environment is not shown in the event highlights.
I am setting the deployment env as the environment for all sentry config files.
Has anyone experienced this before?
Errors are being triggered and sent to sentry correctly, however, the environment name, where the issue is triggered is incorrect.
If I manually capture an exception on a production or QA url, the environment is not shown in the event highlights.
__SENTRY__.hub.captureException("test")
'7b5d999350234ffdb130f8c3696e7685'I am setting the deployment env as the environment for all sentry config files.
process.env.DEPLOY_ENV
init({
environment: DEPLOY_ENV,
dsn: SENTRY_DSN,Has anyone experienced this before?
2 Replies
Tan
@Tonkinese did you ever get a solution to this issue? I am building a NextJS 14 app that has a single build for Kubernetes and the Sentry environment is always set to production. I am trying to get it to use the kubernete node_env.
TonkineseOP
Hey! Yes, I needed to make the deploy environment public