From d9f6ccafc7e441d5c30dd2fa93381f42469b5673 Mon Sep 17 00:00:00 2001
From: Liam White <liam@tetrate.io>
Date: Thu, 31 Jan 2019 07:33:28 +0000
Subject: [PATCH] Add link to ejection event logging config

When reading docs it wasn't immediately clear where to configure the Ejection event logging. This change explicitly links to it.

Signed-off-by: Liam White <liam@tetrate.io>
---
 docs/root/intro/arch_overview/outlier.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/root/intro/arch_overview/outlier.rst b/docs/root/intro/arch_overview/outlier.rst
index 4d1b37fb0f97a..ad4bc1a410e06 100644
--- a/docs/root/intro/arch_overview/outlier.rst
+++ b/docs/root/intro/arch_overview/outlier.rst
@@ -79,6 +79,7 @@ A log of outlier ejection events can optionally be produced by Envoy. This is ex
 during daily operations since global stats do not provide enough information on which hosts are
 being ejected and for what reasons. The log is structured as protobuf-based dumps of
 :ref:`OutlierDetectionEvent messages <envoy_api_msg_data.cluster.v2alpha.OutlierDetectionEvent>`.
+Ejection event logging is configured in the Cluster manager :ref:`outlier detection configuration <envoy_api_field_config.bootstrap.v2.ClusterManager.outlier_detection>`.
 
 Configuration reference
 -----------------------