From 2ff9ea84c70d65cef8a68622e2a798d62c724182 Mon Sep 17 00:00:00 2001 From: JoeOLeary Date: Tue, 11 Feb 2020 10:25:10 +0000 Subject: Update PMSH Documentation * Update PMSH Configuration tables * Update PMSH Logging details Issue-ID: DCAEGEN2-1916 Signed-off-by: JoeOLeary Change-Id: Ife6cf0e26d3047c2d1fed2027eb723f69c4fd727 --- docs/sections/services/pm-subscription-handler/troubleshooting.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/sections/services/pm-subscription-handler/troubleshooting.rst') diff --git a/docs/sections/services/pm-subscription-handler/troubleshooting.rst b/docs/sections/services/pm-subscription-handler/troubleshooting.rst index daf0cb07..07787c41 100644 --- a/docs/sections/services/pm-subscription-handler/troubleshooting.rst +++ b/docs/sections/services/pm-subscription-handler/troubleshooting.rst @@ -15,7 +15,7 @@ Unable to connect to Config Binding Service ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The PMSH may not be able to reach the Config Binding Service. If this is the case you will be able to -see an error connecting to Config Binding Service in Kibana. +see an error connecting to Config Binding Service, by checking the logs in Kibana. Invalid Configuration ^^^^^^^^^^^^^^^^^^^^^ -- cgit 1.2.3-korg