traces_sampler) #2440Description
Problem Statement
I ran into the same problem as was voiced in: getsentry/sentry#28792 (comment), getsentry/sentry#46670, getsentry/sentry#27884.
In short: there is a service that periodically restarts due to heavy load on it, we can't do anything about it. At the moment of restarting the service - there is a large (hundreds of thousands) number of sending logged messages to Sentry. It is impossible to disable messages at all, because we need to control the situation when the service has stopped responding at all.
There is a way to set rate limit for tracing in the documentation (and it is mentioned in getsentry/sentry#46670 (comment)). But there is no way to set rate limit by message text from the logger.
We are using Django, and if we try to do according to the example in the documentation, there is no useful information about the message itself in sampling_context. There's just the transaction, no error, no logger message text, no traceback.
Solution Brainstorm
Please make issues_sampler so that it would be possible to filter a errors before sending it to Sentry.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status