diff --git a/content/rancher/v2.x/en/tools/logging/embedded-elasticsearch/_index.md b/content/rancher/v2.x/en/tools/logging/embedded-elasticsearch/_index.md
new file mode 100644
index 00000000000..6352697b8e5
--- /dev/null
+++ b/content/rancher/v2.x/en/tools/logging/embedded-elasticsearch/_index.md
@@ -0,0 +1,43 @@
+---
+title: Embedded Elasticsearch
+weight: 100
+---
+
+If your organization doesn't have any logging solutions, you can set one up that's embedded within the cluster. You don't have to configure an independent logging server.
+
+>**Notes:**
+>
+>- Embedded Elasticsearch is experimental at this time. Therefore, persistent storage for Embedded Elasticsearch is unavailable.We plan to offer full support in a Rancher release that's yet to be determined.
+>- Embedded Elasticsearch is only available for clusters and not projects.
+>- Setting up Embedded Elasticsearch requires a well provisioned node within the cluster. See the prerequisites below for more details.
+
+## Configuring Cluster Logging
+
+>**Prerequisites:** Your cluster must meet the following hardware requirements:
+>
+>- At least 1 dedicated CPU (2 or more in total).
+>- At least 512 MB RAM.
+
+1. From the **Global** view, open the cluster that you want to configure logging for.
+
+1. From the main menu, select **Tools > Logging**.
+
+1. Select **Embedded Elasticsearch**.
+
+1. Complete the **Embedded Elasticsearch Configuration** form.
+
+    1. From **CPUs and Memory**, set the CPU and memory that elasticsearch can access within your cluster for logging.
+    
+    1. Enter an [Index Pattern](https://www.elastic.co/guide/en/kibana/current/index-patterns.html).
+
+1. Complete the **Additional Logging Configuration** form.
+
+    1. Use the **Add Field** button to add key value pairs used to filter log events.
+
+    1. Enter a **Flush Interval**. This value determines how often the buffered logs are flushed.
+
+1. Click **Save**.
+
+**Result:** Rancher is now configured to send cluster and container events to Embedded Elasticsearch for logging.
+
+You can view your logs by clicking the **Elasticsearch Endpoint** and **Kibana Endpoint** links available on the **Cluster Logging** page.
\ No newline at end of file
diff --git a/content/rancher/v2.x/en/tools/logging/kafka/_index.md b/content/rancher/v2.x/en/tools/logging/kafka/_index.md
new file mode 100644
index 00000000000..d993e575bac
--- /dev/null
+++ b/content/rancher/v2.x/en/tools/logging/kafka/_index.md
@@ -0,0 +1,32 @@
+---
+title: Kafka
+weight: 400
+---
+
+You can configure a Kafka server to log events that occur in your Kubernetes cluster.
+
+>**Prerequisite:** You must have a Kafka server configured.
+
+1. From the **Global** view, open the cluster that you want to configure logging for.
+
+1. From the main menu, select **Tools > Logging**.
+
+1. Select **Kafka**.
+
+1. Complete the **Kafka Configuration** form.
+
+    1. From **Endpoint Type**, select the type of Kafka server you are using: **Zookeeper** or **Broker**.
+
+    1. From the **Endpoint** field, enter the IP address and port for your Kafka server.
+
+        By default, Kafka uses port `9092`.
+
+    1. From the Topic field, enter the name of a Kafka topic that your Kubernetes cluster submits logs to.
+
+1. Complete the **Additional Logging Configuration** form.
+
+    1. Use the **Add Field** button to add key value pairs used to filter log events.
+
+    1. Enter a **Flush Interval**. This value determines how often the buffered logs are flushed.
+
+1. Click **Save**.
\ No newline at end of file