Why are events from a different environment regressing my production environment issue?

Issue

I have a production environment issue that I have resolved. I noticed that events for that issue but belong to another environment such as development or staging are regressing that issue when I am expecting only production events to.

Applies To

• All Sentry users

Symptoms

• Unexpectedly regressed Issues
• Unexpected Alerts

Resolution

Issues will regress when a new event is grouped into a resolved issue. When events get grouped into an issue, by default only the stack trace is considered. Since environment tags are contained outside of the stack trace, the issue will regress when an event with a differing environment tag occurs.

 

The two ways to prevent this is to either extend the default grouping to also take note of environments, or create a separate project for each environment.
 
An example for the fingerprint rule would be:

 

tags.environment:development -> {{default}}, {{ tags.environment }}

 

The above rule will group all events with an environment tag of development separately, but still by the default grouping method of stack trace only.  Any other environments you may have will be unaffected.