diff --git a/docs/platforms/javascript/common/metrics/index.mdx b/docs/platforms/javascript/common/metrics/index.mdx
deleted file mode 100644
index 584f9281be27d5..00000000000000
--- a/docs/platforms/javascript/common/metrics/index.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: Set Up Metrics
-description: "Learn how to measure the data points you care about by configuring Metrics in your JavaScript app."
-sidebar_order: 5500
-sidebar_hidden: true
-notSupported:
- - javascript.capacitor
- - javascript.cordova
- - javascript.cordova
----
-
-
-
-
-
-Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
-
-## Configure Metrics
-
-
-
-## Emit a Counter
-
-Counters are one of the more basic types of metrics and can be used to count certain event occurrences.
-
-To emit a counter, do the following:
-
-
-
-## Emit a Distribution
-
-Distributions help you get the most insights from your data by allowing you to obtain aggregations such as `p90`, `min`, `max`, and `avg`.
-
-To emit a distribution, do the following:
-
-
-
-## Emit a Set
-
-Sets are useful for looking at unique occurrences and counting the unique elements you added.
-
-To emit a set, do the following:
-
-
-
-## Emit a Gauge
-
-Gauges let you obtain aggregates like `min`, `max`, `avg`, `sum`, and `count`. They can be represented in a more space-efficient way than distributions, but they can't be used to get percentiles. If percentiles aren't important to you, we recommend using gauges.
-
-To emit a gauge, do the following:
-
-
-
-## Supported Performance Metric Units
-
-You can pass a unit as a optional parameter of the third argument of the `increment`, `distribution`, `set`, and `gauge` methods.
-
-Units augment metric values by giving meaning to what otherwise might be abstract numbers. Adding units also allows Sentry to offer controls - unit conversions, filters, and so on - based on those units. For values that are unitless, you can supply an empty string or `none`.
-
-These following units are understood by the Sentry backend, but you can supply any arbitrary units you want.
-
-### Duration Units
-
-- `nanosecond`
-- `microsecond`
-- `millisecond`
-- `second`
-- `minute`
-- `hour`
-- `day`
-- `week`
-
-### Information Units
-
-- `bit`
-- `byte`
-- `kilobyte`
-- `kibibyte`
-- `megabyte`
-- `mebibyte`
-- `gigabyte`
-- `gibibyte`
-- `terabyte`
-- `tebibyte`
-- `petabyte`
-- `pebibyte`
-- `exabyte`
-- `exbibyte`
-
-### Fraction Units
-
-- `ratio`
-- `percent`
-
-If you want to explore further, you can find details about supported units in our [event ingestion documentation](https://getsentry.github.io/relay/relay_metrics/enum.MetricUnit.html).
diff --git a/redirects.js b/redirects.js
index e3a91ef9f14b6a..9146ef93027080 100644
--- a/redirects.js
+++ b/redirects.js
@@ -1068,6 +1068,14 @@ const userDocsRedirects = [
source: '/platforms/javascript/tracing/trace-propagation/:path*',
destination: '/platforms/javascript/tracing/distributed-tracing/:path*',
},
+ {
+ source: '/platforms/javascript/metrics/:path*',
+ destination: '/platforms/javascript/tracing/span-metrics/:path*',
+ },
+ {
+ source: '/platforms/javascript/guides/:guide/metrics/:path*',
+ destination: '/platforms/javascript/guides/:guide/tracing/span-metrics/:path*',
+ },
{
source: '/platforms/javascript/tracing/instrumentation/performance-metrics/',
destination: '/platforms/javascript/tracing/span-metrics/',