-
-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config as production but sent sentry as staging env? #929
Comments
@gamesover sorry for the delayed response. is it still troubling you? |
For @gamesover (1.5 years later ⌛) and others who might encounter this problem, here is my workaround.
That way, you can separate these environments in your Sentry monitoring, thus having If you don't set the Note that as @jonekdahl mentioned in #885, you (still) cannot run the |
@pil0u thanks for the great suggestion 👍 |
Hi, my current rails project hosted in heroku is staging. However, according to heroku's recommandation, there is no seperate staging env config in my project. So all info are the same as production. As a result, when exception throw out, I still hope they sent to sentry as staging errors, not production errors.
How to do that?
The text was updated successfully, but these errors were encountered: