This article was updated to support v12.0 and newer of Goliath Performance Monitor.

Article Contents:

• Goliath Server
• Database
• Firewall
• Hypervisor Monitoring
  • VMware vSphere
  • Citrix XenServer
  • Microsoft Hyper-V
•  Application & Desktop Virtualization
  • Citrix Virtual Apps and Desktops Monitoring
  • Citrix Cloud
  • VMware Horizon
• Epic System Pulse Monitoring
• Windows Mobile Device/Tablet Monitoring
• Agent Specifications
• Supported Browsers & Screen Resolutions
• Supported Languages
• Antivirus and Monitoring Solution Exclusions/Filters
• Goliath Master Agent
• Deployment Architectures

Goliath Server

• Virtual Machine or Physical Server
• Windows Server 2012 R2 – 2019 64bit
  • Windows installation English OS required w/o any language packs installed
• Static IP address defined
• Internet Explorer 11 installed.
  • Note: Internet Explorer v11 is required for running backend processes only and is not supported for accessing the console.
• The Goliath server uses IIS. Ensure no additional IIS web sites are running on the Windows server where Goliath is installed. Do not install IIS prior to the technology install.
• The Goliath server must only have 1 enabled NIC card
• Sizing Recommendations:

Database

• Microsoft SQL Server 2016 – 2019
  • Proof of Concept & Product Evaluations use embedded SQL Express 2017 by default. No remote SQL Server or service accounts necessary. 
• Windows Service Account that the installer will grant the database role membership of "db_owner" to the Goliath database is required for Remote SQL Server connectivity (on going)
  
  • This account must also be a Windows Administrator on the Goliath Server
• Windows Account with sysadmin rights to the SQL Server required for installation (one time use)
• SQL Server Configuration Recommendations:
  
  • Set the “Max Server Memory” value as indicated in the below chart
• A dedicated SQL Server is recommended, not shared.  As a monitoring tool GPM is highly transaction requiring dedicated resources. 
• SQL Server Sizing Recommendations based on environment size (recommendations are assuming the SQL Server is remote and default data retention)

  	Proof of Concept Evaluation	Small	Medium	Large	Extra Large	XXL
  Total # of Citrix/VMware Horizon Application & VDI sessions (daily max)	N/A	Up to 1,500	Up to 3,000	Up to 8,000	Up to 15,000	Above 15,000
  CPU	N/A	6vCPU	8vCPU	16vCPU	32vCPU	Technical discussion required for recommendations
  Memory	N/A	32 GB RAM	64 GB RAM	128 GB RAM	256 GB RAM
  # of TempDB’s	N/A	6	8	8	8
  Max Server Memory (MB)	N/A	25500	51245	102490	245760
  Drive space	N/A	Please consult our Database Estimator document
  Drive Type	N/A	N/A	N/A	N/A	SSD drives w/TBs of storage

   

Firewall

• Goliath Server
  • Console Access
    • HTTPS 443* opened inbound to the Goliath Server and outbound from the Goliath Server to the environment
  • Agent Communication
    • HTTPS 443* opened inbound from the agent location to Goliath Server (agent connectivity)
    • TCP 135, 445, 49164 open outbound from the Goliath Server to the agent location (remote agent installation via web console)
  • Hypervisor Monitoring
    • HTTPS 443 opened outbound from the Goliath Server for connection to VMware vCenter
    • HTTP 80 opened outbound from the Goliath Server for connection to Citrix XenServer Pool Master
    • HTTPS 443* opened outbound from the Goliath Server to Microsoft Hyper-V Host/VM
  • Epic System Pulse Module
    • HTTPS 443 opened outbound from the Goliath Server to Epic System Pulse
• Goliath Intelligent Agent Location
  • HTTPS 443* opened outbound from the agent location to the Goliath Server (agent connectivity)
  • TCP 135, 445, 49164 open inbound from the Goliath Server to the agent location (remote agent installation via web console)

* Default ports listed, these maybe be modified however the server and agent port must be the same. 

Hypervisor Monitoring

VMware vSphere

• Versions 4.0 to 7 supported
• Service account with Read Only Rights required

Citrix Hypervisor

• Versions 5.5 to 8.2 supported
• Service account with Read Only Rights required
• NVIDIA GRID K1/K2 card monitoring supported

Microsoft Hyper-V

• Windows Server 2012 R2 – 2019
• Administrator level Credentials to access the Hyper-V Hosts/Servers

Application & Desktop Virtualization

Citrix Virtual Apps and Desktops Monitoring (CVAD)

• Versions 7.6 to 2112 supported
  • Windows 8-10 (Desktop), 2012 R2 – 2019 (Server)
• Service Account with the following privileges is required for Inventory & Metric Collection:
  • Read-Only Admin within Citrix Studio
  • Windows Administrator on the Delivery Controller
    • requires permission to run a windows service
  • If using Citrix PVS, the service account must also be a member of the PVS Farm Administrator group and have Windows Admin Rights on the Provisioning Servers, also to run a service.
• Citrix OData 3.0 (Check your OData version)
• Citrix Profile Manager must be enabled on the VDA for Logon Duration metrics
• PowerShell 3.0 or newer required on the Delivery Controllers and VDAs
• Full Microsoft SQL Server suggested for full implementations of Goliath Performance Monitor
• Support for real-time process metrics can be resource intensive requiring us to determine viability that we would test in the implementation.

Citrix Cloud Monitoring 

• Citrix Customer ID
• Citrix Client ID
• Citrix Secret Key
• Citrix Profile Manager must be enabled on the VDA for Logon Duration metrics
• PowerShell 3.0 or newer required on the VDA
• Full Microsoft SQL suggested for full implementations of Goliath Performance Monitor
• Support for real-time process metrics can be resource intensive requiring us to determine viability that we would test in the implementation.

VMware Horizon Monitoring

• Versions 6.0 to 8.x, 2106 supported
  • Windows 8-10 (Desktop), 2012 R2 – 2019 (Server)
• Service Account with the following privileges:
  • Read-Only Admin within the Horizon Admin Console
  • Windows Administrator Rights on the Connection Server
    • requires permission to run a windows service
• PowerShell v3.0 or newer required
• Full Microsoft SQL suggested for full implementations of Goliath Performance Monitor
• Support for real-time process metrics can be resource intensive requiring us to determine viability that we would test in the implementation.

Epic System Pulse Module

• Service Account with Read-Only Rights
• HTTPS w/ Username enabled for Outgoing Data Services via Epic System Pulse Configuration Editor
• HTTPS enabled for Incoming Data Services via Epic System Pulse Configuration Editor
• Valid SSL Certificate applied to Epic System Pulse Server
  • A copy of the SSL Certificate (*.cer file) is needed for the configuration
• Epic System Pulse Server Address
• Epic resource group name that you'll be connecting to
• Epic resource type id for the above resource group

Windows Mobile Device/Tablet Monitoring

• Windows 8-10 

Agent Specifications

• Virtual Machine or Physical Server
  • Windows Server 2012 R2 - 2019
    • Goliath version 11.8.0 and newer
  • Windows 8 - 10
  • Unix/Linux & Mac up to kernel version 5.1x
• Performance Specs
  • <1% CPU of CPU core
  • 25 MB on Disk
  • ~ 150 MB RAM
• Citrix DDC agent version 11.8.3.2 must be used for versions of Citrix OData 1.0 and 2.0

Supported Browsers & Screen Resolutions

• Chrome v63 and later
• Firefox v50 and later
• Microsoft Edge v85.x and later

Supported Languages

Goliath Technologies supports user experience monitoring for the following:

Citrix Virtual Apps and Desktops:

• Windows installation English OS, Spanish OS (Unicode not supported)
  • Spanish language pack on English OS supported
• Windows installation of German and French
  • Support for Session details and ICA Latency metrics
  • Partial support for Logon Duration metrics
  • No language pack support

VMware Horizon:

• Windows installations English OS

Antivirus and Monitoring Solution Exclusions/Filters

While not a-typical, we have been exposed to client environments which require antivirus filtering, or exclusion rules needing implemented due to the antivirus software conflicting with the Goliath Intelligent Agent. For that reasoning, we do recommend implementing exclusion rules which consist of the following. Please Note: Directory level exclusions are required on the Goliath Server due to the fact that some files are created dynamically in the Goliath application directories.

• Main Goliath Server
  • Directory Exclusions:
    • \Program Files (x86)\MonitorIT\** – This is the install directory of the Goliath Server, the local Agent, and relevant files (please include all subfolders/files)
    • \Windows\System32\inetsrv\** - This is the install directory of the IIS Web Server
    • Ensure recursive exclusions for the subfolders is allowed
  • Process Exclusions:
    • RPMAgent.exe – This is the process which is launched by the Agent’s Service
    • RPMCCS.exe – This is the process which is launched by the Server’s Service
    • AgentService.exe – Process supporting the Agent’s Windows Service
    • w3wp.exe - This is the process for the IIS Web Server
    • Java.exe – Supports hypervisor API communication
    • MonitorITService.exe - Process supporting the Goliath Server’s Windows Service
    • Stunnel.exe – (Optional component) Used to support sending alerts and notifications via SSL/TLS enabled mail servers
    • LogonSimulator.exe - (Optional Component) Used if GAAM is running locally
• VMs/Servers with Agents on them (Citrix machines, VMs, etc.)
  • Directory Exclusions:
    • Paths: “\Program Files\MonitorIT” & “C:\Users\All Users\Goliath”
    • Ensure recursive exclusions for the subfolders is allowed
  • Process Exclusions:
    • RPMAgent.exe – This is the process which is launched by the Agent’s Service
    • AgentService.exe – Process supporting the Agent’s Windows Service
• Goliath Master Agent:
  • Directory Exclusions:
    • \Program Files\MonitorIT\** - This is the install directory of the Master Agent
    • \Windows\System32\inetsrv\** - This is the install directory of the IIS Web Server
    • Ensure recursive exclusions for the subfolders is allowed
  • File/Process Exclusions:
    • RPMAgent.exe – This is the process which is launched by the Agent’s Service
    • AgentService.exe – Process supporting the Agent’s Windows Service
    • w3wp.exe - This is the process for the IIS Web Server for the agent connections
    • MasterAgentModule.dll - file used for IIS Web Server site
    • Java.exe – Supports hypervisor API communication
    • LogonSimulator.exe - (Optional Component) Used if this is also the GAAM Launch Endpoint
• Additional Optional Process Exclusions (if Directory exclusions are not allowed)
  • \Program Files\MonitorIT:
    • AgentEvents.dll
    • AgentService.exe
    • Lua5.1.dll
    • Mfc90.dll
    • mfc90u.dll
    • mfc100.dll
    • mfcm90.dll
    • mfcm90u.dll
    • mfcm100.dll
    • Microsoft.VC90.CRT.manifest
    • Microsoft.VC90.MFC.manifest
    • MISNMP.dll
    • msvcm90.dll
    • msvcp90.dll
    • msvcp100.dll
    • msvcr90.dll
    • msvcr100.dll
    • PSInterface35.dll
    • PSInterface40.dll
    • PSInterfaceLink.dll
    • RpmAgent.exe
    • Uninstall.exe

Goliath Master Agent

• Goliath Master Agent Machine
  • Virtual Machine or Physical Server
  • Windows Server 2012 R2 – 2019 64 bit
  • Static IP address
  • Minimum of 2 vCPU
  • Minimum of 4 GB RAM
  • Minimum of 4 GB Disk Available
  • The Goliath server uses IIS. Ensure no additional IIS web sites are running on the Windows server where Goliath is installed. Do not install IIS prior to the technology install.
• Firewall
  • Goliath Master Agent
    • HTTP 443 opened outbound for agent connection to the main Goliath Server
    • HTTP 443 opened inbound for agent connections
    • TCP 135, 445, 49164 open outbound for remote agent installation via web console
  • Goliath Intelligent Agent
    • HTTP 443 opened outbound for agent connection to the Goliath Master Agent
    • TCP 135, 445, 49164 open inbound for remote agent installation via web console

Deployment Architectures

Goliath Performance Monitor

Goliath Performance Monitor w/ Application Availability Monitor

Goliath Performance Monitor w/ Master Agent