Error loading stack trace from sentry

Summary

After setting up Sentry connection for tracking errors on a C++ project (using Sentry SaaS, not the integrated one), issues and error logs fail to load stack trace.

The issue seems related to the size of the payload returned by Sentry, since I am getting this:

{"message":"Sentry API response is too big. Limit is 1 MB."}

Steps to reproduce

This varies based on the actual error and the size of the stack trace, so it's kind of hard to reproduce.

Example Project

N.A.

What is the current bug behavior?

Sentry API responses bigger than 1MB are treated as errors.

What is the expected correct behavior?

Sentry API responses for some projects, can easily be bigger that 1MB and we should be able to handle those as well.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info


(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)