Now, to pre-pop those params, you need to create a SlaveSettings object with the assumed name of the Slave that'll come up. We do this with the SPOT plugin in 9 and the Balancer (using the core APIs). They'll show up in the Monitor in a blue colour since it's missing the missing the matching SlaveInfo object.

Now, to pre-pop those params, you need to create a SlaveSettings object with the assumed name of the Slave that'll come up. We do this with the SPOT plugin in 9 and the Balancer (using the core APIs). They'll show up in the Monitor in a blue colour since it's missing the missing the matching SlaveInfo object.

I'll admit that I'm unsure how to go about that Edwin. Could you give me a bit more guidance? I can see how to go about setting the params for existing slaves. But I also see what you mean how it takes some time to initialize the new slave instances.

Ah, so the trick here is that if the SlaveSettings object doesn't exist yet, the GetSlaveSettings() will return a new empty object that you can populate with whatever you want. As long as you properly predict what the new Slave will be named (including suffix), you should be able to pre-define its information.