Omnissa Monitor can export Horizon monitoring data, infrastructure and session metrics, to an external analytics platform. Databricks is the supported third-party destination in this release.
Go to Integrations in the left navigation panel. From here you can subscribe to monitoring data and stream it to your analytics platform.
Export status summary
The top of the page summarizes the state of the export.
| Card | Status values | Shows |
|---|---|---|
| Streaming Export | Running or Paused | Real-time data push to your configured destination, with the time of the last push |
In-scope metric categories
| Category | Description | Native collection interval |
|---|---|---|
| Infrastructure | Connection Servers, Unified Access Gateways, and other core Horizon pod components | 5 minutes |
| Session | End-user session, VM, and client metrics | 1 minute |
Exports preserve the following for every data point:
- Timestamp
- Horizon identifiers — pod, pool, VM, user/session, client
- Units
- Sampling interval
This ensures external systems can correctly correlate and aggregate data across sources.
Prerequisites
Before configuring an export, confirm the following:
- You have Omnissa Monitor administrator privileges.
- Your Databricks workspace is reachable from the Omnissa Monitor appliance over the network.
- You have the workspace URL and the authentication credentials required to connect.
Streaming export
On the Integrations page, each configured destination appears as an integration card showing its name, status, and the endpoint it is streaming to.
Each card offers two actions:
| Action | Effect |
|---|---|
| Pause Streaming | Suspends delivery without deleting the configuration |
| Edit Configuration | Opens the configuration for that destination |
Configuration details
The Configuration Details panel summarizes the active settings for the selected destination:
| Setting | Description |
|---|---|
| Workspace URL | The Databricks workspace receiving the data |
| Warehouse ID | The SQL warehouse used for ingestion |
| Catalog | The Unity Catalog catalog that holds the exported data |
| Schema | The schema within that catalog |
| Volume | The volume used for staging exported files |
Health and throughput
The Health & Throughput panel reports delivery health for the destination:
| Metric | Description |
|---|---|
| Last Push | Timestamp of the most recent delivery |
| State | Whether streaming is Running or Paused |
| Errors | Delivery errors reported for this destination |
Review this panel periodically, especially after network or endpoint changes, to confirm exports are being delivered as expected.
Databricks
Omnissa Monitor sends Horizon 8 metrics and event data to a Databricks lakehouse for large-scale analytics, machine learning workflows, and long-term storage.
Data is delivered over HTTP.
Export troubleshooting quick reference
| Symptom | Suggested check |
|---|---|
| No data arriving at endpoint | Confirm the integration card shows Running; verify network reachability and credentials |
| Delivery errors | Check the Errors count in Health & Throughput |
| Delayed delivery | Compare Last Push against the time you expect data to arrive |
| Missing pod in output | Confirm the pod is connected and reporting |
¿Le resultó útil esta página?