On 6/7/24 11:20 AM, Roman Zavarnitsyn wrote: > Sentry.captureException For custom or handled exceptions, works the same way as our automatic uncaught exception handler pretty much, but you capture it manually in this case. > Sentry.captureMessage For plain string informational messages or logs, e.g. if you want to get alerted on some kinds of logs, etc. > Sentry.captureEvent For full-fledged event with everything under your control. All the values you set will be considered and not overridden by the global values (e.g. tags, breadcrumbs, contexts, etc.). Requires more boilerplate from your side. Essentially captureMessage and captureException are just shortcuts for captureEvent provided to your convenience. Does that make sense? — Reply to this email directly, [view it on GitHub](#3465 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AHSHXZIZP35SIDCP3UHEAELZGHFVTAVCNFSM6AAAAABI6XVMKWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TOMBTHE4DQ). You are receiving this because you authored the thread.Message ID: ***@***.***>