How should we setup servicecontrol and serviceinsight/servicepulse in such an environment?
I would recommend the following:
- One ServiceControl instance on Azure ServiceBus ingesting the error queue on ASB
- ServiceControl Audit instance on Azure ServiceBus ingesting the audit queue on ASB
- One audit instance for each MSMQ audit queue
- A bridge for each MSMQ error queue to bridge that error queue over to the ASB error queue (see Bridge configuration options • Messaging Bridge • Particular Docs)
In this setup, you will get a 360 view of your system with all errors managed in a single place and all audit messages visualized.
The reason to go with separate audit instances is to avoid having to move all audit messages over the bridge which can become a bottleneck.
How should we name the instance(s) and paths to install to?
Adding the transport name to at least the audit instances seems reasonable. Perhaps also server name for the MSMQ ones.
Is it possible to pass different paths to the servicecontrol management program?
Not via the UI but as you mention this can be scripted via Powershell, see:
- Managing ServiceControl via PowerShell • ServiceControl • Particular Docs (general)
- Cmdlets and Aliases • ServiceControl • Particular Docs (main instance)
- Managing ServiceControl Audit instances via PowerShell • ServiceControl • Particular Docs (audit instances)
Does this make sense?
Cheers,
Andreas