Getting Started with Solve Actions

Use Solve actions to fix problems or get more information when viewing metrics in your environment. You can now run actions directly from the Solve web interface to interact with entities in the various layers of your organization.

For example, let’s say that you identify a process causing high CPU usage. To solve this problem, you can perform an action to kill the process, or you might decide to disconnect the user session. Real-time monitoring combined with a range of available actions lets you make the best decisions for your organization and users.

Prerequisites

To use Solve actions, you must:

• Have a Solve license
• Upgrade your Real-Time Console and Monitors to version 8.7 or higher. See the upgrade guide for Hybrid Cloud or On-Premises for details.
• Allow your Monitors have access to https://solve.controlup.com over TCP port 443.

Permissions for running Solve actions

You can restrict access to Solve actions by setting permissions in the Security Policy Pane in the Real-Time Console. By default, all Solve users can run actions so if you want to restrict users from running an action, you need to set the Deny to a certain action.

Note that if you have IP restrictions enabled in Solve, users with a restricted IP address can access Solve from the Real-Time Console but they are not allowed to perform actions.

Limitation with the Local Admin role

In the Security Policy Pane, the Local Admin role represents local administrators on remote machines. If a user belongs ONLY to the Local Admin role even if the permission for an action is set to Allow, running the action in Solve fails due to missing permissions.

Setting the permission for the Local Admin user role to Deny on a specific action affects all other user roles. Other users, even those whose permissions are set to Allow, are not allowed to run the Solve action in this case.

Solution

Any user running actions from Solve must belong to more than just the Local Admin role. Ensure that the permission to run the action for both roles is set to Allow.

Perform Actions from Solve

To perform an action from Solve, follow these steps:

1. Go to the Solve Discovery page.
2. In the real-time grid, right-click on the target that you want to perform an action on. The actions menu opens, showing all of the actions you can perform on the selected target. Actions are organized into categories, or you can use the search bar to find a specific action.
3. Select the action that you want to perform on the target.
4. Depending on the action you selected, you might have enter parameters for the action. See Solve Actions: Available Actions for details about specific actions.

To perform an action on multiple targets, select the targets using the checkboxes next to their name before right-clicking on one of the targets.

Perform Actions when the Real-Time Grid isn't Displayed

Sometimes when you drill down into an item in your grid, the real-time grid is replaced with a section listing additional details. In this case, you can open the actions menu at the top-left of the details section.

See Action Status and Details

After you perform an action, an overlay appears on the grid to show the status of your action. The status can either be:

• Success.
  

• Failure.
  

• Partial success. This occurs when the action was successful on some targets, but failed on others.
  

• Running.
  

Click More Info on the action status overlay to open the action details window, including the results and output for each target of the action. The action details are different for built-in actions and script actions.

Built-in action details

The details window for built-in actions shows you only which targets you performed the action on, and if each action was successful.

Script action details

The details window for script actions shows you the output from the script, including any errors, for each target of the action. You can also see details about the script action, such as when it ran, how long it took, and the script exit code.

The Group column indicates groups of targets that have the same output result from the script action. For example, if two targets belong to group 1, then those targets have the same output. You can filter the displayed targets based on their group by selecting the three dots next to the Group column.

Script timeout

If the monitor does not respond within a minute, the following error is displayed:

For both types of actions, you can select a target from the bottom of the window to see the details for that target. To see a history of the actions that were performed in your organization, use the Audit Log.