Sentry: Issue Owner via Tag

[nao3301]

I would love to set an issue Owner with a tag.

like Jone Doe ist the owner for all issues with the tag: 'frontend'

[dcramer]

This is something we've considered, but opted out to avoid complexity today.

Can you describe the use case a bit more? Are you using something like "serviceName=frontend" as a tag?

[nao3301]

yes, we have some microservices and some dev are responsible for some services.

[dleavitt]

Wanted to plus one this and suggest that what's needed here is a subset of the alert settings UI. From my (blurry, poorly-informed) perspective, owner assignment and alerting should be unified into "Rules" or at least share a similar interface. "When this happens, do this."

Use case (basically a long version @nao3301 said):

• We have an application that depends on several underlying services.
• Bug ownership is by service.
• Most of our endpoints use one or more of these services (so url is not a good assignment criterion.)
• Service failures will cause errors in the endpoints consuming them (so file path is not a good assignment criterion.)
• Right now we have all our exceptions tagged by service, if only we could use these tags to assign ownership! :)

[n-peugnet]

Setting ownership via a tag filter would be indeed extremely useful in our case:

We report some errors from external sources via a single aws-lambda using captureMessage so there is no path or url we can filter from. On the other hand it is extremely easy for us to set a tag to each message.

So filtering by tag would solve this problem using for example the following syntax:

tag(service):notifications [email protected]

[caleb15]

I would suggest making the issue owner a tag and then allowing the ability to edit tags. A more generic solution so you don't have to write one-off functionality just for issue owner. This would also have the benefit of allowing people do send alerts based on issue owner. Although now that I think about it that assumes that alert rules run after issue owner rules :thinking:

[LanderMoerkerke]

Is there an update of this will every be implemented?

We would benefit of this kind of functionality due to the fact that all our microservices use the same template and a clear distinction between url or path is not valid per project.

[Finkes]

This would also be very helpful for us. In our case we have a central sentry project collecting issues from various sources. When we send the error to sentry we already add a tag which can be mapped to the owner 1:1. Is this something that you plan for the near future?

[mitsuhiko]

Fixed by #18459