Breaking change: Remove deprecated prometheus metrics from MS

Signed-off-by: Jorge Turrado <[email protected]>

content/docs/2.11/operate/prometheus.md

@@ -29,16 +29,9 @@ The KEDA Webhooks expose Prometheus metrics which can be scraped on port `8080`
 
 ### Metrics Server
 
-> 💡 **DEPRECATED:** Prometheus Metrics exposed from Metrics Server are deprecated, please consume metrics from KEDA Operator.
+The KEDA Metrics Adapter exposes Prometheus metrics which can be scraped on port `8080` at `/metrics`. The following metrics are being gathered:
 
-The KEDA Metrics Adapter exposes Prometheus metrics which can be scraped on port `9022` (this can be changed by setting the `metrics-port` argument for the Metrics Adapter) at `/metrics`. The metrics collected in the Metrics Adapter are only active when the HPA is active (> 0 replicas).
-
-The following metrics are being gathered:
-
-- `keda_metrics_adapter_scaler_errors_total` - The total number of errors encountered for all scalers.
-- `keda_metrics_adapter_scaled_object_error_totals`- The number of errors that have occurred for each scaled object.
-- `keda_metrics_adapter_scaler_errors` - The number of errors that have occurred for each scaler.
-- `keda_metrics_adapter_scaler_metrics_value`- The current value for each scaler's metric that would be used by the HPA in computing the target average.
+- Metrics exposed by the `Operator SDK` framework as explained [here](https://sdk.operatorframework.io/docs/building-operators/golang/advanced-topics/#metrics).
 
 ## Premade Grafana dashboard