Trace represents one simulated packet forwarding path.
Each trace contains multiple ordered steps.
Each step is in a particular state with associated configuration.
State is categorized as final or non-final states.
Each final state has a reason associated.
Each trace must end with a final state (the last step).
<code><code>
|---------------------Trace----------------------|
Step1(State) Step2(State) --- StepN(State(final))
</code></code>
Protobuf type google.cloud.networkmanagement.v1beta1.Trace
Derived from the source and destination endpoints definition specified by
user request, and validated by the data plane model.
If there are multiple traces starting from different source locations, then
the endpoint_info may be different between traces.
Derived from the source and destination endpoints definition specified by
user request, and validated by the data plane model.
If there are multiple traces starting from different source locations, then
the endpoint_info may be different between traces.
ID of trace. For forward traces, this ID is unique for each trace. For
return traces, it matches ID of associated forward trace. A single forward
trace can be associated with none, one or more than one return trace.
A trace of a test contains multiple steps from the initial state to the
final state (delivered, dropped, forwarded, or aborted).
The steps are ordered by the processing sequence within the simulated
network state machine. It is critical to preserve the order of the steps
and avoid reordering or sorting them.
A trace of a test contains multiple steps from the initial state to the
final state (delivered, dropped, forwarded, or aborted).
The steps are ordered by the processing sequence within the simulated
network state machine. It is critical to preserve the order of the steps
and avoid reordering or sorting them.
A trace of a test contains multiple steps from the initial state to the
final state (delivered, dropped, forwarded, or aborted).
The steps are ordered by the processing sequence within the simulated
network state machine. It is critical to preserve the order of the steps
and avoid reordering or sorting them.
A trace of a test contains multiple steps from the initial state to the
final state (delivered, dropped, forwarded, or aborted).
The steps are ordered by the processing sequence within the simulated
network state machine. It is critical to preserve the order of the steps
and avoid reordering or sorting them.
A trace of a test contains multiple steps from the initial state to the
final state (delivered, dropped, forwarded, or aborted).
The steps are ordered by the processing sequence within the simulated
network state machine. It is critical to preserve the order of the steps
and avoid reordering or sorting them.
Derived from the source and destination endpoints definition specified by
user request, and validated by the data plane model.
If there are multiple traces starting from different source locations, then
the endpoint_info may be different between traces.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-28 UTC."],[],[]]
