Quick Tip: How to do ping test in Orchestrator

In this article, we’ll create a lightweight PowerShell action that performs an ICMP ping test and returns the results.

Why Use a Ping Test in Orchestrator?

A ping test can be useful for:

• Verifying network reachability before executing automation tasks.
• Validating DNS name resolution.
• Troubleshooting connectivity issues between Orchestrator and managed endpoints.
• Performing basic health checks as part of larger workflows.
• Quickly confirming that firewall rules and routing are functioning as expected.

Creating the Action

Create a new Action in Aria Automation Orchestrator and select:

Input

Create an input parameter:

PowerShell Script

function Handler($context, $inputs) {

    $target = if ($inputs.target) { $inputs.target } else { "google.com" }

    Write-Host "Pinging $target"

    $result = ping -c 3 $target
    Write-Host ($result -join "`n")

    return @{
        status = "done"
        target = $target
        output = ($result -join "`n")
    }
}

function Handler($context, $inputs) {

    $target = if ($inputs.target) { $inputs.target } else { "google.com" }

    Write-Host "Pinging $target"

    $result = ping -c 3 $target
    Write-Host ($result -join "`n")

    return @{
        status = "done"
        target = $target
        output = ($result -join "`n")
    }
}

Sample Execution

Input:

google.com

Example Output:

Pinging google.com

PING google.com (142.251.223.110): 56(84) bytes of data.
64 bytes from 142.251.223.110: icmp_seq=1 ttl=120 time=4 ms
64 bytes from 142.251.223.110: icmp_seq=2 ttl=120 time=4 ms
64 bytes from 142.251.223.110: icmp_seq=3 ttl=120 time=4 ms

--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss
round-trip min/avg/max = 4/4/4 ms

Pinging google.com

PING google.com (142.251.223.110): 56(84) bytes of data.
64 bytes from 142.251.223.110: icmp_seq=1 ttl=120 time=4 ms
64 bytes from 142.251.223.110: icmp_seq=2 ttl=120 time=4 ms
64 bytes from 142.251.223.110: icmp_seq=3 ttl=120 time=4 ms

--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss
round-trip min/avg/max = 4/4/4 ms

Best Practice

Use ping as a basic reachability test only. This is not a definitive validation of service availability, application health, or end-to-end connectivity. Since Orchestrator may reside on a different subnet, management network, or security zone than the target workload, a failed ping can sometimes be a false negative, where Orchestrator cannot reach the target via ICMP even though the application or workload itself remains fully accessible through its intended network path.