Document Integrated ServicePulse in README

[mikeminutillo]

Added section about Integrated ServicePulse and its hosting capabilities.

[Varorbc]

ServiceControl/src/ServiceControl/Container-README.md

Lines 18 to 24 in 5e72d3f

	docker run -d --name servicecontrol -p 33333:33333 \
	-e TRANSPORTTYPE=RabbitMQ.QuorumConventionalRouting \
	-e CONNECTIONSTRING="host=rabbitmq" \
	-e RAVENDB_CONNECTIONSTRING="http://servicecontrol-db:8080" \
	-e REMOTEINSTANCES='[{"api_uri":"http://audit:44444/api"}]' \
	-e ENABLEDINTEGRATEDSERVICEPULSE="true" \
	particular/servicecontrol:latest --setup-and-run

I noticed that the current documentation contains a few inconsistencies with the existing configuration options.

According to the already published Container-README.md, enabling the integrated ServicePulse should use the SERVICECONTROL_ENABLEINTEGRATEDSERVICEPULSE environment variable, not ENABLEDINTEGRATEDSERVICEPULSE.

In addition, the MONITORING_URL environment variable is also required when running with integrated ServicePulse.

Finally, the correct variable name should be SERVICECONTROL_REMOTEINSTANCES instead of REMOTEINSTANCES.

[mikeminutillo]

Thanks @Varorbc

• Many config settings are shared between instances. To support putting config in a single .env file, any environment variable key that starts with ServiceControl_, ServiceControl.Audit_ or Monitoring_ can omit that prefix and the instance should read it. If both are present, the prefixed version is used to allow overriding for a single instance.
• ENABLED vs ENABLE is a typo, and we will fix it in the documentation. ENABLEINTEGRATEDSERVICEPULSE is the correct key.
• While you can provide MONITORING_URL, it is not required. This can configured from the ServicePulse UI and the value is stored in your browser cache.