Backup & Virtualization
Citrix Virtual Apps and Desktops
Machine catalogs, delivery groups, and live sessions sync into the CMDB as VirtualDesktop CIs; Director session failures open incidents. Session logoff/reset is on the roadmap, not available in this release.
InboundData residency: HYBRID
Request a demoWhat it does
- Machine, delivery group, and session data → a VirtualDesktop CI, its delivery group + machine catalog, and live session_state
- Director session-failure events → incident, with failure category driving severity (license/capacity exhaustion is high; machine failure or registration timeout is medium; connection issues are low)
- One adapter, two control planes: Citrix Cloud REST API or on-prem Studio/Director — chosen per instance
- 5-minute default poll cadence
- Session logoff / profile reset / delivery-group drain is declared in the manifest for the roadmap view; no implementation ships in this release
Data residency
Citrix Cloud's control plane is operated by Citrix (US/EU/APAC regions) while your VDAs and sessions stay on your own infrastructure — resident data is split, hence hybrid.
Event mappings
| External event | Maps to | What happens |
|---|---|---|
| monitor.machine | cmdb.ci.virtual_desktop | Citrix machine (VDA) → VirtualDesktop CI inventory |
| monitor.delivery_group | cmdb.ci.virtual_desktop | Delivery group enriches its machines (name + maintenance/drain state) |
| monitor.session | cmdb.ci.virtual_desktop | Live session → VirtualDesktop session_state (idle/active/disconnected) |
| director.session_failure | incident | Citrix Director session-failure event → incident |
What you configure
- Control plane: Citrix Cloud or on-prem Studio/Director
- Cloud: customer ID + optional regional API base URL
- On-prem: Studio/Director base URL + optional site ID
- Secret reference (client credentials or service-account secret, stored as a secret)
Setup overview
Choose Citrix Cloud or on-prem Studio/Director, supply the connection coordinates, and store the credential as a secret. Session-failure incidents and CI sync both run on the 5-minute poll.
Related features
See TENSOR running on your own estate.
30 minutes, screen-shared, no slides. Bring the process you are least sure we handle and we will start there.