diff --git a/docs/platforms/python/tracing/span-metrics/performance-metrics.mdx b/docs/platforms/python/tracing/span-metrics/performance-metrics.mdx
deleted file mode 100644
index 3869d416a690e2..00000000000000
--- a/docs/platforms/python/tracing/span-metrics/performance-metrics.mdx
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Sending Performance Metrics
-description: "Learn how to attach performance metrics to your Sentry transactions."
-sidebar_order: 20
-notSupported:
-  - javascript.cordova
----
-
-The SDK supports sending performance metrics data to Sentry. These are numeric values attached to transactions that are aggregated and displayed in Sentry.
-
-## Custom Measurements
-
-In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry.
-
-To set a performance measurement, you need to supply the following:
-
-- name (`string`)
-- value (any numeric type - `float`, `integer`, etc.)
-- unit (`string`, defaults to the string `none` if omitted)
-
-Sentry supports adding arbitrary custom units, but we recommend using one of the [supported units listed below](./#supported-measurement-units).
-
-<PlatformContent includePath="performance/custom-performance-metrics" />
-
-<Include name="custom-measurements-units-disclaimer.mdx" />
-
-## Supported Measurement Units
-
-Units augment measurement 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`.
-
-### 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/platform-includes/metrics/metrics-units/python.mdx b/platform-includes/metrics/metrics-units/python.mdx
deleted file mode 100644
index 47cd35f8b3e63a..00000000000000
--- a/platform-includes/metrics/metrics-units/python.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
-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`.
-
-### 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`
-
-For more details about supported units, see our [event ingestion documentation](https://getsentry.github.io/relay/relay_metrics/enum.MetricUnit.html).