- 3 minutes to read

Remote Actions

Nodinite Remote Actions empower authorized Users to securely execute corrective commands on monitored Resources—without risky admin access or IT bottlenecks. Instantly resolve issues, reduce downtime, and delegate control to the right people, all with a full Audit Trail.

Secure, role-based actions for business and IT users
Instantly resolve common problems and reduce downtime
All actions are fully logged for compliance and traceability
No global administrator rights required

Why Use Remote Actions?

Organizations with monitored integration landscapes often face a bottleneck: only administrators can act when a service fails. Remote Actions breaks this pattern by delegating specific, safe commands to the right people—without granting them broad system access.

Benefit	Description
Faster incident response	Authorized users fix problems immediately—no waiting for IT
Full Audit Trail	Every action is logged for security and compliance
Self-Service recovery	Empower business teams to resolve issues in their own domain
Least-privilege design	Delegates only the specific commands needed, not full admin rights
Auto-healing potential	Combine with monitoring thresholds for automated recovery workflows

How Remote Actions Work

Remote Actions are available in the Control Center section of the Actions button within a Monitor View. A Nodinite Administrator grants the Execute Action permission per Role and per Monitor View.

graph TD A[" User spots issue
in Monitor View"] --> B{" Execute Action
permission granted?"} B -->|"Denied"| C[" Remote Actions
not visible"] B -->|"Allowed"| D[" Remote Actions menu
visible in Control Center"] D --> E[" User selects action
e.g. Start Service"] E --> F[" Monitoring Agent
executes command on Resource"] F --> G[" Resource recovers
to healthy state"] F --> H[" Log Audit entry
created automatically"] G --> I[" Monitor View updates
to OK state"] style A fill:#87CEEB style B fill:#FFD700 style C fill:#FF6B6B style D fill:#87CEEB style E fill:#87CEEB style F fill:#87CEEB style G fill:#90EE90 style H fill:#90EE90 style I fill:#90EE90

Diagram: Remote Actions workflow—from detecting an issue in a Monitor View to executing a corrective command via a Monitoring Agent, with automatic Audit Trail logging.

Note
All Remote Actions are audited for security and compliance.

Enabling Remote Actions

Remote Actions are a privilege—they must be explicitly granted by a Nodinite Administrator. Access is controlled through the Execute Action permission in the Permission Set for Monitor Views:

Open Administration > Access Management > Roles
Select or create a Role
Navigate to the Monitor permissions tab
For each Monitor View, set Execute Action to Allow
Save the role and assign it to the relevant Users

Edit rights for Remote Actions in a Monitor View role configuration.

Tip
Follow the least-privilege principle: grant only the Execute Action permission needed, not full administrator access. This keeps your Audit Trail clean and your security posture strong.

See Permission Set for Monitor Views for a complete reference of all Monitor View permissions, including Inherited, Allow, and Deny behaviour.

When to Use Remote Actions

Use Remote Actions whenever you want to delegate specific operational tasks without granting admin access. Below are real-world examples from common Nodinite Monitoring Agents:

Monitoring Agent	Scenario	Executed Action	Business Value
Windows Server Monitoring Agent	Windows Service has stopped	Start	Let the finance department restart a single Windows Service without contacting IT. Saves time and money for all parties.
BizTalk Server Monitoring Agent	Receive Location has stopped	Enable	Let IT-operations restart a single BizTalk Receive Location without being a BizTalk Admin. Nodinite Remote Actions save time and money.

Tip
Hundreds of Remote Actions are implemented across Nodinite Monitoring Agents. You don't need to be a global administrator to fix problems—delegate the right action to the right person.

BizTalk Server

Sample Remote Actions from the Nodinite BizTalk Server Monitoring Agent Resources:

Example 1: Suspended Messages (resumable)	Example 2: Receive Location

Example of Remote Actions in BizTalk resources where operators can resume suspended messages and enable receive locations without full BizTalk administrator rights.