summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/pm-mapper/troubleshooting.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/sections/services/pm-mapper/troubleshooting.rst')
-rw-r--r--docs/sections/services/pm-mapper/troubleshooting.rst4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/sections/services/pm-mapper/troubleshooting.rst b/docs/sections/services/pm-mapper/troubleshooting.rst
index c025fb0c..b71c45d7 100644
--- a/docs/sections/services/pm-mapper/troubleshooting.rst
+++ b/docs/sections/services/pm-mapper/troubleshooting.rst
@@ -96,7 +96,7 @@ Make sure Config Binding Service is up and running and the **ip + port** combina
====
-**Missing configuration on Consul**
+**Invalid configuration on Consul**
::
@@ -127,4 +127,6 @@ Make sure Config Binding Service is up and running and the **ip + port** combina
**PM Mapper** logs this information when connected to Consul, but cannot find a valid JSON configuration.
+This can occur if the PM Mapper is deployed through Cloudify Manager or CLAMP when the default 'pm-mapper-filter' field is left unchanged as this default is configured to work with the DCAE Dashboard. If this is the cause for the invalid configuration then it can be resolved by removing the surrounding quotes on the object.
+