Skip to content

fix serving directory path #1015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 18, 2019
Merged

fix serving directory path #1015

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/serving/setting-up-a-logging-plugin.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ kubectl apply --recursive --filename config/monitoring/100-namespace.yaml \
```

In the commands above, replace `<path-of-fluentd-daemonset-config>` with the
Fluentd DaemonSet configuration file, e.g. `config/monitoring/stackdriver`.
Fluentd DaemonSet configuration file, e.g. `config/monitoring/logging/stackdriver`.

**NOTE**: The deployment above will not affect the fluentd sidecar of existing
pods. Developers need to redeploy their app to get the newest configuration for
Expand All @@ -76,7 +76,7 @@ backends. For example, if they desire Elasticsearch&Kibana, they have to deploy
the Elasticsearch and Kibana services. Knative provides this sample:

```shell
kubectl apply --recursive --filename third_party/config/monitoring/elasticsearch
kubectl apply --recursive --filename third_party/config/monitoring/logging/elasticsearch
```

See [here](/serving/installing-logging-metrics-traces.md) for deploying the
Expand Down