Best practices for ServicePulse/ServiceInsight in dealing with multiple ServiceControl instances

[Jatinder Brar]

Good Morning,

I have a monitoring box set up on which I have ServiceControl, ServicePulse and ServiceInsights installed. I have three ServiceControl Deployed Instances via ServiceControl Management Utility as I have three different transport configurations I am monitoring. From a ServicePulse/ServiceInsights perspective what would you recommend as far as how to monitor these three endpoints? At present for ServicePulse I'm switching ServiceControl instances by updating the service_control_url constant in app.constants; for ServiceInsights I'm updating the Service Url specified in the Connect Endpoint Explorer. Seems a bit hacky, I was just wondering if there was a different approach you recommend? Please let me know your thoughts. Thanks.

[Sean Feldman]

Hi Jatinder,

If you're using SP/SC for production, be aware that for production systems it is recommended to limit the number of instances per machine to one. (http://docs.particular.net/servicecontrol/installation#transport-support-using-the-servicecontrol-management-utility-to-upgrade-servicecontrol-instances).

You can configure SP to run as 3 different instance using running under IIS (http://docs.particular.net/servicepulse/install-servicepulse-in-iis).

For the SC there's no way to overcome this. Also note that SC control is intended for development debugging, not production monitoring.

[Sean Feldman]

Correction: SI (ServiceInsight) is intended for development debugging, not SC (ServiceControl) as I've replied incorrectly before.