github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-07 20:21:20 +00:00
Code Issues Projects Releases Wiki Activity

Corrected some typos

Browse Source
This commit is contained in:
George Kuan
2015-04-26 19:37:14 -07:00
parent e061043cf1
commit 9f64d009e0
17 changed files with 25 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/logging.md
View File

@@ -23,7 +23,7 @@ Kibana logging dashboard will be available at https://130.211.152.93/api/v1beta1
Visiting the Kibana dashboard URL in a browser should give a display like this:
![Kibana](kibana.png)
To learn how to query, fitler etc. using Kibana you might like to look at this [tutorial](http://www.elasticsearch.org/guide/en/kibana/current/working-with-queries-and-filters.html).
To learn how to query, filter etc. using Kibana you might like to look at this [tutorial](http://www.elasticsearch.org/guide/en/kibana/current/working-with-queries-and-filters.html).
You can check to see if any logs are being ingested into Elasticsearch by curling against its URL. You will need to provide the username and password that was generated when your cluster was created. This can be found in the `kubernetes_auth` file for your cluster.
```
@@ -38,7 +38,7 @@ Cluster logging can be turned on or off using the environment variable `ENABLE_N
to `false` to disable cluster logging.
The type of logging is used is specified by the environment variable `LOGGING_DESTINATION` which for the
GCE provider has the default value `elasticsearch`. If this is set to `gcp` for the GCE provder then
GCE provider has the default value `elasticsearch`. If this is set to `gcp` for the GCE provider then
logs will be sent to the Google Cloud Logging system instead.
When using Elasticsearch the number of Elasticsearch instances can be controlled by setting the