In choosing a suitable Web Server for a production installation of Redgate Monitor, consider the following requirements:

High-speed connection to its Base Monitor if it's on a different machine, over secure RPC, to collect the monitoring data, authenticate users and other tasks. 

• Slow communication with a Base Monitor will be a limiting factor in the overall performance of the monitoring system.  See: Hardware and performance guidelines for more details.
• If the Base Monitor machine is in a different domain, you will need to ensure port 7399 is open in the firewall.
• It is important to get a robust hardware and software installation because you will not be able to log in to the web front-end if its associated Base Monitor cannot be reached. 

Accessibility by any PC or device from which you want to view the Redgate Monitor Web interface

• The web interface uses JavaScript, so make sure JavaScript is enabled in your web browser. 
  • If you have performance issues, try switching to a different supported browser.

The default Redgate Monitor Web Server or IIS 10 or later (Windows only).

• You can install the default Redgate Monitor Web Server, a self-contained server that uses Kestrel under the hood.
  • The Redgate Monitor Web Server service is called Redgate Monitor Web Service on Windows and redgatemonitor-web.service on Linux.
  • Details for setting up SSL can be found on: Configuring HTTPS for the default Redgate Monitor web server.
• You can also use IIS to host Redgate Monitor, details for setting up an IIS Server can be found on: Installing Redgate Monitor on IIS.

Other hardware and software requirements:

• Should always be switched on.
• Uses about 1GB of space.
• Must be running currently supported versions of Windows or Linux. See Supported platforms for details.