413 Request Entity Too Large #2798

Activity

1. davidpaley

   added

   Status: Needs Triage

   on Aug 4, 2020
2. davidpaley commented on Aug 5, 2020

   

   davidpaley

   on Aug 5, 2020

   Author

   More actions

   Ok, I could resolve this filtering the different breadcrumbs of the object it sends to entry:

   Sentry.init({
     dsn:
       'dns_url',
     beforeBreadcrumb(breadcrumb, hint) {
       if (breadcrumb.category === 'console') {
         return null
       }
       return breadcrumb
     },
   })
   

   In my case, it sends too many breadcrumbs with the category 'console' so the error object serialized to a string was greater than the maximum size.

   👍React with 👍12Reacted by Michael D, Adithya Reddy, Björn S. von Ubisch, repl-sarath, balarayen-blippar, Kaat, Roshan Choxi, Abdalla Abdelnasser, Daniel Vilela, Kunal Gupta and 2 more

   👎React with 👎2Reacted by Dmytro Chumak and Roman Martynov
3. davidpaley

   closed this as completedon Aug 5, 2020
4. avalanche1 commented on Dec 12, 2021

   

   avalanche1

   on Dec 12, 2021

   More actions

   This is absurd, that it would drop the reports altogether, SILENTLY.

   👍React with 👍18Reacted by Yuichi Yogo, Mikhail P, Fego Ahia, Finlay Smith, Francis Pérez Padilla, Daniel Vilela, Edward Goubely, Jeffrey Biles, AndreKR, Tal Peretz and 8 more
5. andirsun commented on Jan 9, 2023

   

   andirsun

   on Jan 9, 2023

   Last edited by andirsun

   More actions

   For me was to reduce normalizeDepth from 10 to 3 (default value for next js).

   Before

   Sentry.init({
       dsn: config.SENTRY_DSN,
       environment: config.SENTRY_ENV,
      normalizeDepth: 10,
      ...
     })
   

   After

   Sentry.init({
       dsn: config.SENTRY_DSN,
       environment: config.SENTRY_ENV,
       ...
     })