ControlUp Automate

Automate script actions to maximize resources, optimize end user’s experience and supplement your troubleshooting efforts.

ControlUp Real-Time DX connects to a multitude of data sources, collecting granular real-time metrics, logs and configuration data across the compute, storage, network and service layers of the modern EUC data center. An advanced rule evaluator is able to instantly check and evaluate thousands of state changes in each of the many logical objects the real-time engine monitors, providing a granular incident trigger mechanism. Combining the granular incident trigger mechanism together with the Script Action module is the basis for ControlUp Automate. A script action(s) can be chained to any incident trigger. Once the trigger condition is met the script action(s) is executed.

Automation offers powerful capabilities and many use cases, among them:

  • Dynamic Optimization of Digital Experience – By measuring real-time digital experience metrics from within the users’ sessions and allocating additional resources if these are available
  • Resource Efficiency Optimization – Dynamically optimize allocation of resources to busy consumers while claiming back idle resources from non busy consumers allowing for higher density without sacrificing performance.
  • Augmented Troubleshooting – leveraging real-time triggers to collect additional contextual information needed for troubleshooting (collecting relevant logs, performance counters and more from the time of the incident and sending all information attached as part of the ticket).
  • Self-driven EUC Operations – performing specific corrective actions in response to logs and events.

ControlUp Automate comes with few failsafe mechanisms:

  • Security context – In order to execute Automated Actions one needs to be part of a dedicated security role (automation Admins)
  • Throttling – Automated Actions which are executed repeatedly are automatically throttled to prevent system overload.
  • Auditing – Each action invocation is logged and a detailed event with action invocation result is written in the application log.