> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/labs/traffic-lens.md).

# Traffic Lens

![Traffic Lens utilization](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FRdt7xD9DCIwHECqPkzCS%2Fve20261112v5-tutorial-traffic-util.png?alt=media)

GUI-guided tutorial for utilization and bandwidth paint on the topology. Deep gallery: Visualize, Traffic, and Present.

## Goal

Watch how busy links look (utilization / bandwidth), use the Traffic dock, and know when rates are live vs sample.

## Why Traffic Lens exists

Operate tells you nodes are up. Traffic Lens paints **how busy** links look so you can demo congestion, failover, and hand off to [Packet capture](/labs/packet-capture.md) without leaving the canvas.

## GUI tutorial

### Step 1 - Enter Visualize -> Traffic

1. Open a lab with running nodes (or start them in Operate)
2. Click **Visualize** on the workspace bar
3. Open **Traffic** from the tool rail or **More -> Traffic**

![Traffic utilization](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FRdt7xD9DCIwHECqPkzCS%2Fve20261112v5-tutorial-traffic-util.png?alt=media)

|                  |                                                   |
| ---------------- | ------------------------------------------------- |
| **What you see** | Traffic Lens chrome; links colored by utilization |
| **Expected**     | Mode stays Visualize; Traffic UI is active        |

### Step 2 - Read utilization paint

1. Look at link colors / thickness for utilization
2. Hover or select a busy link
3. If everything is zero - generate traffic (ping) or use sample traffic if offered

### Step 3 - Switch to Bandwidth mode

![Bandwidth mode](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FLGwjtzJFo2YAQHcJgZU2%2Fve20261112v5-tutorial-traffic-bandwidth.png?alt=media)

1. Open the Traffic **mode** picker
2. Choose **Bandwidth** (and try one more mode such as packets/sec or heatmap when listed)
3. Confirm the canvas paint updates for the new mode

|                  |                                                       |
| ---------------- | ----------------------------------------------------- |
| **What you see** | Bandwidth (or selected) mode active                   |
| **Expected**     | Mode label changes; paint follows the selected metric |

### Step 4 - Use the Traffic dock

![Traffic dock](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FrIQNHmfmxEb7KJYxrLIp%2Fve20261112v5-tutorial-traffic-dock.png?alt=media)

1. Open dock tabs: **Interfaces**, **Flows**, Timeline, Packets, Protocols, Events, Alerts (as offered)
2. Switch tabs without leaving Visualize
3. Select a link on the canvas to focus the dock

|                  |                                        |
| ---------------- | -------------------------------------- |
| **What you see** | Dock tables / charts for the selection |
| **Expected**     | Tab switches stay in Traffic Lens      |

### Step 5 - Live vs sample honesty

* When nodes are running and fabric stats are available, rates reflect **live** link statistics
* When backends are quiet, the UI may show **sample** or zero rates - that is the visualization framework, not a fake WAN guarantee
* Forensics: [Packet capture](/labs/packet-capture.md). Path quality: [Link inspector and impairment](/labs/link-inspector-and-impairment.md)

### Step 6 - Leave Traffic

1. Switch Visualize lens to Overview, or mode back to Design / Operate
2. Or press Escape from Present if you nested demo chrome

## Expected result

* Utilization and Bandwidth modes both reachable from Traffic
* Dock tabs work without leaving the lab
* You can jump to Capture or Impairment on a selected link

## If it fails

* No paint -> Start nodes; ping across the path; wait a few seconds
* Mode does nothing -> refresh the lab; confirm Visualize + Traffic
* Classic Link Inspector hidden -> use Traffic dock first, or exit Traffic - see [Link inspector and impairment](/labs/link-inspector-and-impairment.md)

## Related

* Visualize, Present, and Preview
* [Packet capture](/labs/packet-capture.md)
* [Link inspector and impairment](/labs/link-inspector-and-impairment.md)
* [Operate and consoles](/labs/operate-and-consoles.md)
* Toolbars and More menu


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vex-nx.com/labs/traffic-lens.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.