Command map

monitor traceroute

Live mtr-style traceroute that updates continuously.

Ze command

Registry path
monitor traceroute
Usage
monitor traceroute <destination> [max-hops <max-hops>] [timeout <timeout>] [probes <probes>] [do-not-fragment <honor-cache|bypass-cache>]
Mode
read-only, offline
Wire method
ze-traceroute:monitor-traceroute
Backends
any backend
Task support
required: the MCP server always answers with a task handle
Subcommands
none: this command takes no subcommand
Pipes, always
json, ndjson, table, text, yaml, raw, no-more, save, match, count, first, last, display, fill, resolve, origin
Pipes, while streaming
log
Pipes, local process only
save
Answer shape
tab
Address fields
addr

Description

Shows each hop with running RTT statistics. Keeps probing so you can watch
path changes and latency shifts over time.

Arguments

NameTypeRequiredValuesSummaryDescription
destinationstringyesany value of this typeHost or IP address to trace.The value is the first bare word of the command, or follows the destination keyword. A host name is resolved in either address family, and the family of the answer selects ICMPv4 or ICMPv6.
max-hopsuintnoany value of this typeMaximum number of hops.The value is the largest time-to-live the stream probes. Absent, the stream probes 30 hops, and the one-shot round of the API surfaces probes 16.
timeoutstringnoany value of this typeTimeout duration, accepted and not read.The value is accepted in Go duration syntax, 1s to 30s, and then not read: each probe round waits one second for every answer.
probesuintnoany value of this typeNumber of probes per hop, accepted and not read.The value is accepted in the range 1 to 10 and then not read: a probe round sends one probe at each time-to-live.
do-not-fragmentenumnohonor-cache bypass-cacheDon't Fragment mode, accepted and not read.The keyword takes one of two values, honor-cache or bypass-cache, as on show traceroute, and then neither is read: a probe round sends every probe with the Don't Fragment bit off.

Mapping status

No vendor equivalent has been curated yet for this Ze command.

Juniper Junos MX

No equivalent is listed for this vendor yet.

Cisco IOS XR

No equivalent is listed for this vendor yet.

Nokia SR OS

No equivalent is listed for this vendor yet.

VyOS

No equivalent is listed for this vendor yet.