feat: Add docs about what captureMessage does (#11258)

mydea · web-flow · commit ad051c935684 · 2024-09-18T08:24:37.000Z
diff --git a/docs/platforms/android/usage/index.mdx b/docs/platforms/android/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/apple/common/usage/index.mdx b/docs/platforms/apple/common/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/dart/usage/index.mdx b/docs/platforms/dart/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/dotnet/common/usage/index.mdx b/docs/platforms/dotnet/common/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/elixir/usage/index.mdx b/docs/platforms/elixir/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/flutter/usage/index.mdx b/docs/platforms/flutter/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/go/common/usage/index.mdx b/docs/platforms/go/common/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/java/common/usage/index.mdx b/docs/platforms/java/common/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/javascript/common/usage/index.mdx b/docs/platforms/javascript/common/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/kotlin-multiplatform/usage/index.mdx b/docs/platforms/kotlin-multiplatform/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/native/common/usage/index.mdx b/docs/platforms/native/common/usage/index.mdx
@@ -34,4 +34,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/php/common/usage/index.mdx b/docs/platforms/php/common/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/php/guides/laravel/usage/index.mdx b/docs/platforms/php/guides/laravel/usage/index.mdx
@@ -21,6 +21,8 @@ In Laravel, you can pass an error object to `captureException()` to get it captu
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
 
 ## Customization
diff --git a/docs/platforms/powershell/usage/index.mdx b/docs/platforms/powershell/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/python/usage/index.mdx b/docs/platforms/python/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/ruby/common/usage/index.mdx b/docs/platforms/ruby/common/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/rust/common/usage/index.mdx b/docs/platforms/rust/common/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/unity/usage/index.mdx b/docs/platforms/unity/usage/index.mdx
@@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
diff --git a/docs/platforms/unreal/usage/index.mdx b/docs/platforms/unreal/usage/index.mdx
@@ -25,4 +25,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th
 
 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.
 
+Messages show up as issues on your issue stream, with the message as the issue name.
+
 <PlatformContent includePath="capture-message" />
