Errors not being logged when local variable data is included

Will

Posted on
Aug 11 2018

Hi,

We use Raygun to log errors from both our React client and our Django backend. Typically 500 errors logged by the client create a corresponding backend error. This worked until about a week ago, when we noticed that out client was logging 500 errors, but no corresponding errors were being logged for the backend.

The temporary "solution" was to log Python errors using a configuration {'transmit_global_variables': False, 'transmit_local_variables': False}, which our testing confirms causes the backend errors to be logged as expected. This solution was motivated by noticing that the few backend errors that were getting logged successfully tended to have much less frame data than was typical.

So there appears to us to be some issue with logging errors that are either too large or contain too much metadata. I confirmed that the Python client was not throwing any errors when pickling the data or sending it and confirmed with ngrep that data was getting transmitted to the Raygun server.

Obviously logging errors with no context data is not ideal, so we're hoping to find a solution.

Thanks! Will


Reply