From 76fe7415764798fd03fbbb97a3cf605661b5fd6c Mon Sep 17 00:00:00 2001 From: Andrew Chen Date: Mon, 8 May 2017 10:10:47 -0700 Subject: [PATCH] grammar nits --- .../debug-application-cluster/logging-elasticsearch-kibana.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md b/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md index c51a3dd875..ead9f2b377 100644 --- a/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md +++ b/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md @@ -13,10 +13,10 @@ On the Google Compute Engine (GCE) platform, the default logging support targets in the [Logging With Stackdriver Logging](/docs/user-guide/logging/stackdriver). This article describes how to set up a cluster to ingest logs into -[Elasticsearch](https://www.elastic.co/products/elasticsearch), and view +[Elasticsearch](https://www.elastic.co/products/elasticsearch) and view them using [Kibana](https://www.elastic.co/products/kibana), as an alternative to Stackdriver Logging when running on GCE. Note that Elasticsearch and Kibana -cannot be set up automatically in the Kubernetes cluster hosted on +cannot be setup automatically in the Kubernetes cluster hosted on Google Container Engine, you have to deploy it manually. To use Elasticsearch and Kibana for cluster logging, you should set the