In this scenario, Butler SOS will run as a Node.js app on the Windows server itself.
1. Install Node.js
Any recent Node version should work fine, but if in doubt the latest LTS version is usually a good idea.
2. Select a directory from which Butler SOS will be run
This can be pretty much anywhere, in this example d:\tools\butler-sos will be used.
3. Get Butler SOS
Get the desired Butler SOS version and extract it into the directory above.
4. Install Node.js dependencies
From d:\tools\butler-sos\src, run
npm i to install the various Node.js modules used by Butler SOS. Depending on your server configuration you may get some warnings about (for example) Python not being installed, these can usually be ignored.
The configuration file is used the same way as when Butler SOS runs on Docker, with one exception:
The path to the certificates used to authenticate with Sense must be specified in the config file. With Docker the certificate path is always the same, but with Windows you need to specify where the certificate files are located.
For example, if the certificate files exported from Sense are stored in d:\secrets\sensecert, the config file would look like this when used on Windows:
... # Certificates to use when querying Sense for healthcheck data. Get these from the Certificate Export in QMC. cert: clientCert: d:\secrets\sensecert\client.pem clientCertKey: d:\secrets\sensecert\client_key.pem clientCertCA: d:\secrets\sensecert\root.pem
There is a dependency between the name of the YAML configuration file and the NODE_ENV environment variable.
production.yaml file can be named anything, as long as it matches the value of the
NODE_ENV environment variable.
For example, if the config file is called
production.yaml, the NODE_ENV environment variable should be set to ‘production’.
In Windows you do this by
set NODE_ENV=production in a command prompt, or even better as a server wide setting.
A tool like Butler SOS should of course start automatically when the server it runs on is restarted. This can be achieved in at least a couple of ways:
By far the best option is to turn Butler SOS into a Windows service. That way it will be started on server boot, restarted if it fails etc. There are various tools for doing this, with NSSM being a very, very good one. Butler SOS has been set in lots of Sense clusters this way.
You can also use a Node process monitor such as PM2 to monitor the Butler SOS process, and restart it if it for some reason crashes. PM2 is not entirely easy to use on Windows though.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how Butler SOS can be improved.