Merge pull request #1308 from loganhz/log

Fix logging and monitoring issue
This commit is contained in:
Denise
2019-03-24 23:49:39 -07:00
committed by GitHub
5 changed files with 5 additions and 10 deletions
@@ -29,6 +29,6 @@ After adding all the Fluentd servers, you have the option to select **Enable Gzi
## SSL Configuration
If your Fluentd servers are using TLS, you need to select **Use TLS**. Provide the **CA Certificate PEM**. You can copy and paste the certificate or upload it using the **Read from a file** button.
If your Fluentd servers are using TLS, you need to select **Use TLS**. If you are using a self-signed certificate, provide the **CA Certificate PEM**. You can copy and paste the certificate or upload it using the **Read from a file** button.
>**Note:** Fluentd does not support self signed certificates.
>**Note:** Fluentd does not support self-signed certificates when client authentication is enabled.
@@ -28,7 +28,7 @@ If your Kafka cluster is using SSL for the **Broker**, you need to complete the
1. Provide the **CA Certificate PEM**. You can either copy and paste the certificate or upload it using the **Read from a file** button.
>**Note:** Kafka does not support self signed certificates.
>**Note:** Kafka does not support self-signed certificates when client authentication is enabled.
### SASL configuration
@@ -25,11 +25,6 @@ If you are using rsyslog, please make sure your rsyslog authentication mode is `
If your Syslog server is using **TCP** protocol and uses TLS, you need to select **Use TLS** and complete the **Encryption Configuration** form.
1. Select whether or not you want to verify your SSL. If the **Enabled - Input trusted server certificate** option is selected, a certificate section is enabled. You can either copy and paste the certificate or upload them by **Read from a file**.
* If you are using a self-signed certificate, provide the **CA Certificate PEM**.
* If you are using a certificate from a certificate authority, provide your **Trusted Server Certificate Chain**.
1. Provide the **Client Private Key** and **Client Certificate**. You can either copy and paste them or upload them by using the **Read from a file** button.
- You can use either a self-signed certificate or one provided by a certificate authority.
@@ -14,8 +14,8 @@ After you've enabled monitoring at either the [cluster level]({{< baseurl >}}/ra
Rancher's dashboards are available at multiple locations:
- **Cluster Dashboard**: From the **Global** view, navigate to the cluster.
- **`System` Project Dashboard**: From the **Global** view, navigate to the **System** project of the cluster.
- **Node Metrics**: From the **Global** view, navigate to the cluster. Select **Nodes**. Find the individual node and click on its name. Click **Node Metrics.**
- **Workload Metrics**: From the **Global** view, navigate to the project. Select **Workloads > Workloads**. Find the individual workload and click on its name. Click **Workload Metrics.**
- **Pod Metrics**: From the **Global** view, navigate to the project. Select **Workloads > Workloads**. Find the individual workload and click on its name. Find the individual pod and click on its name. Click **Pod Metrics.**
- **Container Metrics**: From the **Global** view, navigate to the project. Select **Workloads > Workloads**. Find the individual workload and click on its name. Find the individual pod and click on its name. Find the individual container and click on its name. Click **Container Metrics.**
@@ -35,7 +35,7 @@ As an [administrator]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/global
1. Click **Save**.
**Result:** A single application,`project-monitoring`, is added as an [application]({{< baseurl >}}/rancher/v2.x/en/catalog/apps/) to the cluster's `system` project. After the application is `active`, you can start viewing [project metrics](#project-metrics) through the [Rancher dashboard]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/monitoring/#rancher-dashboard) or directly from [Grafana]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/monitoring/#grafana).
**Result:** A single application,`project-monitoring`, is added as an [application]({{< baseurl >}}/rancher/v2.x/en/catalog/apps/) to the project. After the application is `active`, you can start viewing [project metrics](#project-metrics) through the [Rancher dashboard]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/monitoring/#rancher-dashboard) or directly from [Grafana]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/monitoring/#grafana).
## Project Metrics