After the appliance is deployed, complete the steps below to access the web console, set up your organization, and connect your Horizon 8 data sources.
Accessing the Web Console
After deployment, configure DNS to map the appliance IP address to the fully qualified domain name you assigned during deployment, then browse to that address.
At the login screen, enter admin as the username, along with the admin password you set during OVF deployment, and click Sign In.
Note: Changing the admin password from the root console does not update the web console password. To sign in to the web console, use the admin password you provided during OVF deployment.
Organization Setup
On first login you are prompted to set a name for your organization and tenant. This represents your organization's monitoring scope within Omnissa Monitor.
Fields marked with an asterisk (*) are mandatory.
| Field | Required | Description |
|---|---|---|
| Organization name | Yes | The name of your organization within Omnissa Monitor — for example, EUC-OM-ORG2. Must be unique. |
| Group organization name | No | An optional parent grouping used to associate related organizations. |
Enter the required values and click Get Started.
Note: A valid license key must be validated after sign-in and before you create your organization. See License Validation for the key required by your entitlement.
Connecting Data Sources
Data sources represent the infrastructure components being monitored by this instance of Omnissa Monitor.
Available sources
The Data Sources page presents each source type as a card under Available sources. Each card offers a Connect action to begin the onboarding wizard and a Learn More link to the relevant documentation.
| Source | Card description | Procedure |
|---|---|---|
| Horizon | Connect your Horizon 8 pod to be monitored on this instance of Omnissa Monitor. | Connecting a Horizon 8 pod |
| vSphere | Connect your vCenters to be monitored on this instance of Omnissa Monitor. | Connecting a vSphere data source |
Note: You can onboard up to two Horizon 8 pods and up to two vCenters.
Once a source is connected it moves from Available sources to Connected sources.
Connecting a Horizon 8 pod
Each Horizon pod corresponds to one Horizon Connection Server cluster. On the Horizon card, click Connect to start the onboarding wizard. Onboarding a Horizon 8 pod takes approximately 15 minutes to complete.
Before you begin
Select configuration mode
The Select configuration mode dialog determines how the Omnissa Monitor data collector and data processor modules are deployed relative to the data sources they monitor. Select a mode and click Connect to continue.
Co-located mode
The data collector modules and the data processor are deployed as a single instance. Data sources (Horizon 8 Connection Servers, Unified Access Gateways, and end-user machines) send their data to that centralized data collector.
Recommended for: deployments with two or fewer Horizon 8 pods.
Because the collector and processor are co-located on the Omnissa Monitor appliance itself, no separate collector host is required.
- Prepare credentials. Have the Horizon Connection Server and Unified Access Gateway credentials ready. These are required to establish a trusted connection between the Horizon data sources and Omnissa Monitor.
- Check connectivity. Ensure the required ports and protocols are open between the Omnissa Monitor appliance and the Horizon data sources. See Port and protocol requirements.
1. Configure Horizon Data Collector
Specify the Horizon Data Collector that Omnissa Monitor will communicate with for this pod.
Configuration fields (mandatory):
- Horizon Data Collector FQDN/IP address — for example,
10.68.170.47 - Horizon Pod display name — for example,
om-hent-dc
In co-located mode, the data collector runs on the Omnissa Monitor appliance, so this is the appliance's own FQDN or IP address.
Port: Each pod requires its own dedicated port on the data collector. The default is 31883. Specify the port along with the collector address (for example, 10.68.170.47:31883). When you add a second pod, assign it a different port, such 31884. Two pods cannot share one port.
2. Horizon Connection Server
Provide credentials for one Connection Server in the Horizon pod cluster. Omnissa Monitor uses these credentials to discover and monitor all Connection Servers and end-user VDI/RDSH VMs in the cluster.
Note: Provide a direct Connection Server URL. Do not use the load balancer URL that fronts the Connection Server cluster.
3. Unified Access Gateways (Optional)
This step connects UAG appliances for monitoring. Configure the UAG load balancer and each individual UAG VM.
Load Balancer configuration:
- Enter the load balancer Name and FQDN or IP address.
- Click Save to store the load balancer configuration.
Individual Gateway VMs:
- Click Add under the Gateways section.
- Provide the UAG Name and IP/FQDN for each UAG appliance.
When all steps are complete, click Save & Exit and verify that the pod shows a Connected status.
If the pod does not reach Connected, see Troubleshooting.
Managing connected data sources
After onboarding, select Data Sources in the left navigation panel to manage your connected sources. From there you can:
- Review the status of each connected Horizon pod
- Edit Connection Server credentials
- Add or remove Unified Access Gateway appliances
Next steps
- Connect vCenter for infrastructure monitoring — vSphere Infrastructure Observability
- Send monitoring data to an external platform — Data Export and Integrations
Esta página foi útil?