Many of our critical error messages are being dropped with the following error:
2017-07-13 17:16:49,394 203 ERROR 682 base | Sentry responded with an error: HTTP Error 413: Request Entity Too Large (url: https://sentry.io/api/<REDACTED ID>/store/) Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/raven/transport/threaded.py", line 172, in send_sync super(ThreadedHTTPTransport, self).send(url, data, headers) File "/usr/local/lib/python2.7/dist-packages/raven/transport/http.py", line 43, in send ca_certs=self.ca_certs, File "/usr/local/lib/python2.7/dist-packages/raven/utils/http.py", line 66, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 435, in open response = meth(req, response) File "/usr/lib/python2.7/urllib2.py", line 548, in http_response 'http', request, response, code, msg, hdrs) File "/usr/lib/python2.7/urllib2.py", line 473, in error return self._call_chain(*args) File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) HTTPError: HTTP Error 413: Request Entity Too Large
We are using python + django + celery, raven version 6.1.0. This particular error happened inside a celery task.
Having a truncated error message is fine, but entirely dropping it defeats the whole point of using Sentry.
I am guessing that we need to limit the size of the message on the client side? How can we do that?
I don’t want to disable breadcrumbs, but would be okay with dropping earlier or larger breadcrumbs if too large, replacing them with a “dropped” message or something like that.