Hi! we're using the python SDK, and our codebase has a good few manual sentry_sdk.capture_message, as described on https://docs.sentry.io/platforms/python/usage/#capturing-messages. Some of these usages are during exception handling and set to level error (yeah, colleagues colleaguing) and while arguably not 'the rightest way', at least according to docs, my expectation is that these would come under 'errors', which doesn't happen atm. On Sentry any such call comes under issues (with corresponding 'level').
IMO this should happen for at least (manual) messages with level 'error' or higher, though in Sentry any level shows under issues, so for consistency maybe should be the same for all.
Thanks for this product btw, looking forward to its success, cheers!
Hi! we're using the python SDK, and our codebase has a good few manual
sentry_sdk.capture_message, as described on https://docs.sentry.io/platforms/python/usage/#capturing-messages. Some of these usages are during exception handling and set to level error (yeah, colleagues colleaguing) and while arguably not 'the rightest way', at least according to docs, my expectation is that these would come under 'errors', which doesn't happen atm. On Sentry any such call comes under issues (with corresponding 'level').IMO this should happen for at least (manual) messages with level 'error' or higher, though in Sentry any level shows under issues, so for consistency maybe should be the same for all.
Thanks for this product btw, looking forward to its success, cheers!