WendyOS Docs
Wendy CLIcloud

wendy cloud ping

Ping a cloud-enrolled device through the tunnel broker

Syntax

wendy cloud ping [--device <name>] [flags]

Examples

wendy cloud ping --help

Arguments

Argument notation from the CLI: [--device <name>]. Angle brackets mark required values; square brackets mark optional values. See Details for command-specific validation.

Flags

Flags below include inherited options. Types and defaults come from the CLI source. An empty default means no value is configured.

FlagTypeDefaultDescription
--broker-urlstring(empty)Tunnel broker host:port
--cloud-grpcstring(empty)Cloud gRPC endpoint (optional when a default session is set via 'wendy auth use')
--count / -cint0Stop after this many echoes (0 = until Ctrl+C)
--devicestring(empty)Device name (skips interactive picker)
--interval / -iduration1sTime between echoes
--jsonboolfalseOutput in JSON format

Output

Output depends on the operation and selected target. Use the command help for additional guidance..

JSON output

The global --json option requests machine-readable output. The CLI also selects JSON mode when no interactive terminal is attached. Support and payloads are command-specific; this flag does not guarantee a single JSON document for commands that stream logs or invoke build tools. Consult Details before parsing command output.

Exit codes

The CLI entry point returns 0 on success and for its user-cancelled or default-cleared results. Other returned errors exit with 1 and print a diagnostic to stderr. Some operations may terminate through subprocess or signal handling; do not infer application health from the CLI exit code alone.

Common errors

Check argument values and flag combinations against the synopsis above. For discovery, build, port, and readiness failures, see deployment troubleshooting. Command-specific constraints are in Details.

See also

Details

Measures agent round-trip time through Wendy Cloud. PKI sessions use the agent version RPC over an authorized tunnel; legacy sessions use datagram echoes. A reply proves the device's agent is up and measures true end-to-end round-trip time. No ICMP sockets or privileges are involved.

Use the command help for additional guidance.

On this page