Ignore specific messages

ericgsmith → changed the visibility of the branch 3408332-ignore-specific-messages to hidden.

I'm not 100% sure this is needed, since an issue can be discarded in Sentry, or the before_send hook can be used as you mentioned. But if there's demand we could work on it.

Not sure how many users monitor this issue queue to weigh in on feature requests, but maybe folks could give this a thumbs up if it'd be useful.

Answering part of my own question: If you discard an event in Sentry, you still have to send it there, which could cost 150ms time (which is a lot!), unless Sentry or Sentry Relay is running locally.

So discarding in Sentry is a workaround, but not a great workaround.

Better to use the before_send hook or add this feature.

Let's add this feature to the 6.x branch

mfb → changed the visibility of the branch 6.x to hidden.

mfb → closed merge request !20

Thanks Mark - I've tested the port to branch 3408332-port with Drupal 10.3 and its working as expected for me

ericgsmith → changed the visibility of the branch 3408332-backport-4.x to hidden.

Pushed a 4.x backport to the fork - have a need for this patch on a site that is still on 4.x due to an older version of Sentry - hiding MR but there in case anybody is in a similar situation.

mfb → reopened merge request !20

This is I think ready to be committed to 5.x branch, and then we can backport to 4.x as well

mfb → changed the visibility of the branch 3408332-backport-4.x to active.

Automatically closed - issue fixed for 2 weeks with no activity.