Monitor and Manage HVR Remote Listener Processes

Question

Are there best practices for monitoring and managing HVR remote listener processes?

Environment

HVR

Answer

Yes. The following sections describe the best practices in HVR to monitor and manage HVR's remote listener process (or agent as it is referred to) for both Linux and Windows environments:

Linux

The best practice for monitoring and managing HVR's remote listener processes on Linux is to run the agent under systemd, which takes care of starting the agent on demand.

If systemd is not available on your operating system (typically a non-Linux Unix), then you can create a xinetd or inetd managed service.

Xinetd is an open-source daemon that manages the internet connections on many modern Unix and Unix-like servers. Read Installing HVR on Unix or Linux for creating a HVR listener service for either systemd or xinetd.

Both the systemd and xinetd mechanisms for creating a HVR listener service ensure that the services start automatically after a system reboot.

In some instances you might encounter an error where after a certain number of simultaneous connections (e.g. 10), the remote child process starts to fail. You can set up a maintenance job to catch that error and receive alerts via Email, Slack, or SNMP.

Windows

The best practice for monitoring and managing HVR remote listener processes on Windows is to run the agent as a Windows Service and have it auto-start. We also recommend configuring a recovery option to restart the service automatically after a failure. For more information, see Configuring Remote Installation of HVR on Windows.