Skip to content

Detect oversized events and attempt to reduce their size #4822

@adinauer

Description

@adinauer

Problem Statement

Events can be too large due to mulitple reasons, e.g.:

  • too many breadcrumbs
  • large breadcrumbs
  • too much / large customer context data / attributes
  • large stack traces (e.g. caused by recursion)

Also see: #910

Solution Brainstorm

Look at what other SDKs do.

Ruby removes breadcrumbs and if that's not enough, reduces stack trace size.

Could also provide a callback for allowing customers to drop what they prefer.

Reducing stack trace size (#4818) could also be performed conditionally if this is implemented.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions