I have a question around captureMessage semantics. Specifically, given that the naming of the API does not imply error conditions I assumed ‘messages’ would be collected on Sentry’s UI without being treated as errors. However I’m realizing they’re collected under ‘Issues’, alongside errors, and pretty much treated same as errors are. I suspect based on this, that the difference between captureMessage and captureException is not really a semantic one but rather specific to the parameters they accept?
Is there any approach whereby I can capture arbitrary, non-error ‘events’ that aren’t treated as errors by Sentry?