diff --git a/docs/platforms/python/usage/index.mdx b/docs/platforms/python/usage/index.mdx index 81fb1850156166..42ffb4a76bbdcf 100644 --- a/docs/platforms/python/usage/index.mdx +++ b/docs/platforms/python/usage/index.mdx @@ -27,8 +27,8 @@ While capturing an event, you can also record the breadcrumbs that lead up to th ## Capturing Messages -Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually. +While uncommon, you can also manually capture a plain message without an exception. -Messages show up as issues on your issue stream, with the message as the issue name. +Messages show up as issues on your issue stream, with the message as the issue name so avoid serializing payloads or embedding unique values in the message text, instead attach additional information via tags and context. diff --git a/platform-includes/capture-message/python.mdx b/platform-includes/capture-message/python.mdx index 99633596312116..98178c5cdb8bfa 100644 --- a/platform-includes/capture-message/python.mdx +++ b/platform-includes/capture-message/python.mdx @@ -1,5 +1,8 @@ ```python import sentry_sdk -sentry_sdk.capture_message('Something went wrong') +sentry_sdk.capture_message( + 'Something went wrong', + tags={'component': 'worker', 'region': 'us-west-2'} +) ```