diff --git a/docs/product/issues/issue-details/low-value-span-issues/index.mdx b/docs/product/issues/issue-details/low-value-span-issues/index.mdx
new file mode 100644
index 00000000000000..bb2e17fd556d82
--- /dev/null
+++ b/docs/product/issues/issue-details/low-value-span-issues/index.mdx
@@ -0,0 +1,38 @@
+---
+title: Low-Value Span Issues
+sidebar_order: 55
+description: "Learn more about Low-Value Span issues and how to reduce noise and span volume in your traces."
+---
+
+<Alert title="Currently in Beta">
+
+Low-Value Span Issues are currently in open beta.
+
+</Alert>
+
+A _low-value span issue_ is raised when Sentry detects a span that is sent frequently but adds little value to your traces. These spans clutter the trace view, make it harder to spot the spans that actually help with debugging, and contribute to your stored span volume and cost.
+
+Sentry groups matching spans into a single low-value span issue. These issues are set to `LOW` priority and are excluded from the default issue search. To find them, open the **Configuration** view on the **Issues** page or filter with `issue.category:configuration`.
+
+## Issue Details
+
+The **Issue Details** page for a low-value span issue summarizes the offending span and its projected impact:
+
+- **Affected span** — A summary of the span Sentry detected. Click through to see matching spans in [Trace Explorer](/product/explore/trace-explorer/).
+- **Span count** — Projected 30-day volume of this span, extrapolated from a recent sample.
+- **Estimated cost** — Projected 30-day cost of ingesting and storing this span, when available.
+- **Average duration** — Average duration of this span in the analyzed sample.
+
+## Fixing a Low-Value Span Issue
+
+How you fix the issue depends on where the span comes from. The **Troubleshooting** section of the issue tells you whether the span originates from SDK automatic instrumentation or from your own custom instrumentation, and shows a ready-to-use snippet for filtering it.
+
+[Seer Autofix](/product/ai-in-sentry/seer/autofix/) can also generate and apply the fix for you directly from the issue.
+
+- **Automatic instrumentation** — Drop the span before it is sent using your SDK's filtering options. See <PlatformLink to="/configuration/filtering/">Filtering</PlatformLink>.
+- **Custom instrumentation** — Remove the span from your code, or add attributes that make it more useful. See <PlatformLink to="/tracing/instrumentation/custom-instrumentation/">Custom Instrumentation</PlatformLink>.
+
+## Limitations
+
+- Low-value span issues do not trigger workflow notifications.
+- They are excluded from the default issue search. Open the **Configuration** view on the **Issues** page or filter with `issue.category:configuration` to find them.