From fd1698cb91d9e6c2765b1612afb56e6a2e213ef3 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Fri, 20 Jul 2018 15:20:19 -0700 Subject: [PATCH] added logging high level --- Note: | 0 content/rancher/v2.x/en/tools/_index.md | 20 ++++++++++++++++++++ 2 files changed, 20 insertions(+) create mode 100644 Note: diff --git a/Note: b/Note: new file mode 100644 index 00000000000..e69de29bb2d diff --git a/content/rancher/v2.x/en/tools/_index.md b/content/rancher/v2.x/en/tools/_index.md index f2035de11ea..b9890a91279 100644 --- a/content/rancher/v2.x/en/tools/_index.md +++ b/content/rancher/v2.x/en/tools/_index.md @@ -44,3 +44,23 @@ _Notifiers_ are services that inform you of alert events. You can configure noti Alerts and notifiers are powered by [Prometheus Alertmanager](https://prometheus.io/docs/alerting/alertmanager/). +## Logging + +Rancher can integrate with popular external services used for event streams, telemetry, or search. Rancher can integrate with the following services: + +- Embedded Elasticsearch (experimental) + >**Note:** This option is available only at the cluster level. +- Elasticsearch +- splunk +- kafka +- syslog + +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. + +You can configure these services to collect logs at either the cluster or project level. + +## Pipelines + +Rancher \ No newline at end of file