diff --git a/content/rancher/v2.5/en/monitoring-alerting/_index.md b/content/rancher/v2.5/en/monitoring-alerting/_index.md
index c6d16e6d6e9..f59f886c6fe 100644
--- a/content/rancher/v2.5/en/monitoring-alerting/_index.md
+++ b/content/rancher/v2.5/en/monitoring-alerting/_index.md
@@ -62,6 +62,10 @@ As an [administrator]({{<baseurl>}}/rancher/v2.5/en/admin-settings/rbac/global-p
 > - Make sure your cluster fulfills the resource requirements. The cluster should have at least 1950Mi memory available, 2700m CPU, and 50Gi storage. A breakdown of the resource limits and requests is [here.](#setting-resource-limits-and-requests)
 > - When installing monitoring on an RKE cluster using RancherOS or Flatcar Linux nodes, change the etcd node certificate directory to `/opt/rke/etc/kubernetes/ssl`.
 
+{{% tabs %}}
+{{% tab "Rancher v2.5.8" %}}
+
+### Enable Monitoring for use without SSL
 
 1. In the Rancher UI, go to the cluster where you want to install monitoring and click **Cluster Explorer.**
 1. Click **Apps.**
@@ -71,6 +75,46 @@ As an [administrator]({{<baseurl>}}/rancher/v2.5/en/admin-settings/rbac/global-p
 
 **Result:** The monitoring app is deployed in the `cattle-monitoring-system` namespace.
 
+### Enable Monitoring for use with SSL
+
+1. Follow the steps on [this page]({{<baseurl>}}/rancher/v2.5/en/k8s-in-rancher/secrets/) to create a secret in order for SSL to be used for alerts.
+ - The secret should be created in the `cattle-monitoring-system` namespace. If it doesn't exist, create it first.
+ - Add the `ca`, `cert`, and `key` files to the secret.
+1. In the Rancher UI, go to the cluster where you want to install monitoring and click **Cluster Explorer.**
+1. Click **Apps.**
+1. Click the `rancher-monitoring` app.
+1. Click **Alerting**.
+1. Click **Additional Secrets** and add the secrets created earlier.
+ 
+**Result:** The monitoring app is deployed in the `cattle-monitoring-system` namespace.
+
+When [creating a receiver,]({{<baseurl>}}/rancher/v2.5/en/monitoring-alerting/configuration/alertmanager/#creating-receivers-in-the-rancher-ui) SSL-enabled receivers such as email or webhook will have a **SSL** section with fields for **CA File Path**, **Cert File Path**, and **Key File Path**. Fill in these fields with the paths to each of `ca`, `cert`, and `key`. The path will be of the form `/etc/alertmanager/secrets/name-of-file-in-secret`.
+
+For example, if you created a secret with these key-value pairs:
+
+```yaml
+ca.crt=`base64-content`
+cert.pem=`base64-content`
+key.pfx=`base64-content`
+```
+
+Then **Cert File Path** would be set to `/etc/alertmanager/secrets/cert.pem`.
+
+{{% /tab %}}
+{{% tab "Rancher v2.5.0-2.5.7" %}}
+
+1. In the Rancher UI, go to the cluster where you want to install monitoring and click **Cluster Explorer.**
+1. Click **Apps.**
+1. Click the `rancher-monitoring` app.
+1. Optional: Click **Chart Options** and configure alerting, Prometheus and Grafana. For help, refer to the [configuration reference.](./configuration)
+1. Scroll to the bottom of the Helm chart README and click **Install.**
+
+**Result:** The monitoring app is deployed in the `cattle-monitoring-system` namespace.
+
+{{% /tab %}}
+
+{{% /tabs %}}
+
 ### Default Alerts, Targets, and Grafana Dashboards
 
 By default, Rancher Monitoring deploys exporters (such as [node-exporter](https://github.com/prometheus/node_exporter) and [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics)) as well as default Prometheus alerts and Grafana dashboards (curated by the [kube-prometheus](https://github.com/prometheus-operator/kube-prometheus) project) onto a cluster.