Trace Route Runbook
A Trace Route runbook traces the path a packet takes from the ObserveOps server to the target monitor and returns one row per hop.
When to Use
Use Trace Route to confirm reachability through a specific gateway, locate a hop that is dropping packets, or verify a routing change took effect.
Fields
| Field | What to enter |
|---|---|
| Runbook Name | A short, unique name. |
| Description | One line on what the runbook returns. |
| Runbook Category | Diagnostics, Performance Monitoring, Troubleshooting, System Management, Log Collection, Network Config, or Integration. |
| Monitor | Pick by Group, Tag, IP/Host, or Monitors. |
| Maximum Hops | The TTL ceiling for the trace. Defaults to 30. |
| Probes | The number of probes sent per hop. Defaults to 3. |
| Timeout | Seconds to wait at each hop before marking it unreachable. |
note
The Trace Route form has no Credential Profile, no Script Language, no Script, and no parsing script. The result screen shows the hop list with address and round-trip time.
Steps
- Open Settings > Plugin Library > Runbook and click Create Runbook Plugin.
- Pick Trace Route from the top menu.
- Fill in the fields above.
- Click Test to run the trace once and show the hops.
- Click Save.