L0006 - Monitor Service¶
TO DO
Fix - we probably won't supply a Monitor service. We'll use some new IIS and ASP.NET settings instead, that prevent RMS from going to sleep.
The Monitor service has a simple job; to ensure that the POS server is responsive to requests, and to prevent it from sleeping due to inactivity so that activities such as background tasks continue to run.
Configuration (Optional)¶
The installer will install and configure the Monitor service with default settings that are appropriate for most environments. This help section describes the settings that are available, in case you want to change the default behavior.
The Monitor service is deployed to the same folder as the RMS Server executable files. Accordingly, the Monitor service uses the same appsettings.json file (or environment variables) as POS. It uses some of the same settings as POS, as well as introducing its own:
| Field Name | Description |
|---|---|
| SeqUrl | The URL to the Seq logging server, e.g. https://logs.fusionrms.com. |
| SeqApiKey | The API key to use for the Seq logging server. |
| MonitorBaseUrl | Base URL for tenants that use a Request Url Prefix to identify a tenant from an incoming HTTP request. This is not normally used outside of development, as production sites use Request Url Host to differentiate sites (e.g. each tenant gets its own host name). The default value is http://localhost. |
| MonitorTenantsFolder | The absolute path to the folder where the RMS Server's tenants.json file can be found. By default this is the App_Data folder of where the Monitor service is installed. You can change this value if you decide to run the Monitor service from a different folder than the default RMS Server folder. |
| MonitorIntervalSeconds | Number of seconds to wait between monitor requests, in seconds. The default value is 60 seconds. |
As the Monitor service is installed in the same folder as POS, the default settings are appropriate for most installations.
Warning
If testing the Monitor service on localhost, avoid using an HTTPS connection to a self-signed SSL certificate. The self-signed certificate is not readable when the program is run under a service account (you will receive an SSL error).
This scenario is typically only encountered when testing on a developer workstation.