github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-30 06:54:01 +00:00
Code Issues Projects Releases Wiki Activity

Update sidecar logging console output in docs

Browse Source
This commit is contained in:
Satnam Singh 2015-07-18 22:47:42 +01:00
parent 715f2c488f
commit 69668365ce
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
contrib/logging/fluentd-sidecar-es/README.md
View File

@ -15,12 +15,12 @@ In order to make this work, you have to add a few things to your pod config:
4. The `FILES_TO_COLLECT` environment variable in the sidecar container, telling it which files to collect logs from. These paths should always be in the mounted volume.
To try it out, make sure that your cluster was set up to log to Elasticsearch when it was created (i.e. you set `LOGGING_DESTINATION=elasticsearch`), then simply run
```
```console
kubectl create -f logging-sidecar-pod.yaml
```
You should see the logs show up in the cluster's Kibana log viewer shortly after creating the pod. To clean up after yourself, simply run
```
```console
kubectl delete -f logging-sidecar-pod.yaml
```

4
contrib/logging/fluentd-sidecar-gcp/README.md
View File

@ -15,12 +15,12 @@ In order to make this work, you have to add a few things to your pod config:
4. The `FILES_TO_COLLECT` environment variable in the sidecar container, telling it which files to collect logs from. These paths should always be in the mounted volume.
To try it out, make sure that your cluster was set up to log to Google Cloud Logging when it was created (i.e. you set `LOGGING_DESTINATION=gcp` or are running on Container Engine), then simply run
```
```console
kubectl create -f logging-sidecar-pod.yaml
```
You should see the logs show up in the log viewer of the Google Developer Console shortly after creating the pod. To clean up after yourself, simply run
```
```console
kubectl delete -f logging-sidecar-pod.yaml
```