summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--docs/development/design/logging.rst32
-rw-r--r--docs/release/configguide/sdc_config_guide.rst2
2 files changed, 25 insertions, 9 deletions
diff --git a/docs/development/design/logging.rst b/docs/development/design/logging.rst
index 05f3f5b..5fbaeb9 100644
--- a/docs/development/design/logging.rst
+++ b/docs/development/design/logging.rst
@@ -9,7 +9,23 @@ Installation
Currently, we use the `sample configuration`_ in Istio to install fluentd::
cd clover/logging
- kubectl apply -f install
+
+First, install logging stack Elasticsearch, Fluentd and Kibana::
+
+ kubectl apply -f install/logging-stack.yaml
+
+Then configure fluentd for istio::
+
+ kubectl apply -f install/fluentd-istio.yaml
+
+Note that, it must be done in two steps. If you run ``kubectl apply -f install``
+instead, the mixer adapter may fail to intialize because the target service can
+not be found. You may find an error message from mixer container::
+
+ 2018-05-09T02:43:14.435156Z error Unable to initialize adapter:
+ snapshot='6', handler='handler.fluentd.istio-system', adapter='fluentd',
+ err='adapter instantiation error: dial tcp: lookup fluentd-es.logging on
+ 10.96.0.10:53: no such host'.
.. _sample configuration: https://istio.io/docs/tasks/telemetry/fluentd.html
@@ -50,14 +66,14 @@ Istio defines when to log by creating a custom resource ``rule``. For example:
apiVersion: "config.istio.io/v1alpha2"
kind: rule
metadata:
- name: newlogtofluentd
- namespace: istio-system
+ name: newlogtofluentd
+ namespace: istio-system
spec:
- match: "true" # match for all requests
- actions:
- - handler: handler.fluentd
- instances:
- - newlog.logentry
+ match: "true" # match for all requests
+ actions:
+ - handler: handler.fluentd
+ instances:
+ - newlog.logentry
This rule specifies that all instances of ``newlog.logentry`` that matches the
expression will be handled by the specified handler ``handler.fluentd``. We
diff --git a/docs/release/configguide/sdc_config_guide.rst b/docs/release/configguide/sdc_config_guide.rst
index be0c86e..b95b6cf 100644
--- a/docs/release/configguide/sdc_config_guide.rst
+++ b/docs/release/configguide/sdc_config_guide.rst
@@ -314,7 +314,7 @@ following command:
istio-system jaeger-deployment NodePort 10.105.94.85 <none> 16686:32174/TCP
istio-system prometheus NodePort 10.97.74.230 <none> 9090:32708/TCP
-In the example above, the Jaeger tracing web-based UI will be available on port 32171 and
+In the example above, the Jaeger tracing web-based UI will be available on port 32174 and
the Prometheus monitoring UI on port 32708. In your browser, navigate to the following
URLs for Jaeger and Prometheus respectively::