Logging is helpful because it allows you to:
- Capture and analyze the state of your cluster
- Look for trends in your environment
- Save your logs to a safe location outside of your cluster
- Stay informed of events like a container crashing, a pod eviction, or a node dying
- More easily debug and troubleshoot problems
Rancher supports integration with the following services:
How Logging Integrations Work
Rancher can integrate with popular external services used for event streams, telemetry, or search. These services can log errors and warnings in your Kubernetes infrastructure to a stream.
These services collect container log events, which are saved to the
/var/log/containers directory on each of your nodes. The service collects both standard and error events. You can then log into your services to review the events collected, leveraging each service's unique features.
When configuring Rancher to integrate with these services, you'll have to point Rancher toward the service's endpoint and provide authentication information.
Additionally, you'll have the opportunity to enter key-value pairs to filter the log events collected. The service will only collect events for containers marked with your configured key-value pairs.
Note: You can only configure one logging service per cluster or per project.
The Docker daemon on each node in the cluster should be configured with the (default) log-driver:
json-file. You can check the log-driver by running the following command:
$ docker info | grep 'Logging Driver'
Logging Driver: json-file
You can configure logging at either cluster level or project level.
- Cluster logging writes logs for every pod in the cluster, i.e. in all the projects. For RKE clusters, it also writes logs for all the Kubernetes system components.
- Project logging writes logs for every pod in that particular project.
Logs that are sent to your logging service are from the following locations:
- Pod logs stored at
- Kubernetes system components logs stored at
Enabling Cluster Logging
As an administrator or cluster owner, you can configure Rancher to send Kubernetes logs to a logging service.
From the Global view, navigate to the cluster that you want to configure cluster logging.
Select Tools > Logging in the navigation bar.
Select a logging service and enter the configuration. Refer to the specific service for detailed configuration. Rancher supports integration with the following services:
(Optional) Instead of using the UI to configure the logging services, you can enter custom advanced configurations by clicking on Edit as File, which is located above the logging targets. This link is only visible after you select a logging service.
With the file editor, enter raw fluentd configuration for any logging service. Refer to the documentation for each logging service on how to setup the output configuration.
If the logging service is using TLS, you also need to complete the SSL Configuration form.
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.
You can generate a self-signed certificate using an openssl command. For example:
openssl req -x509 -newkey rsa:2048 -keyout myservice.key -out myservice.cert -days 365 -nodes -subj "/CN=myservice.example.com"
If you are using a self-signed certificate, provide the CA Certificate PEM.
(Optional) Complete the Additional Logging Configuration form.
Optional: Use the Add Field button to add custom log fields to your logging configuration. These fields are key value pairs (such as
foo=bar) that you can use to filter the logs from another system.
Enter a Flush Interval. This value determines how often Fluentd flushes data to the logging server. Intervals are measured in seconds.
Include System Log. The logs from pods in system project and RKE components will be sent to the target. Uncheck it to exclude the system logs.
Click Test. Rancher sends a test log to the service.
Note: This button is replaced with Dry Run if you are using the custom configuration editor. In this case, Rancher calls the fluentd dry run command to validate the configuration.
Result: Rancher is now configured to send logs to the selected service. Log into the logging service so that you can start viewing the logs.