Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

Trace

import type { Trace } from "https://googleapis.deno.dev/v1/networkmanagement:v1.ts";

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). |---------------------Trace----------------------| Step1(State) Step2(State) --- StepN(State(final))

interface Trace {
endpointInfo?: EndpointInfo;
forwardTraceId?: number;
steps?: Step[];
}

§Properties

§
endpointInfo?: EndpointInfo
[src]

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.

§
forwardTraceId?: number
[src]

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.

§
steps?: Step[]
[src]

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.