View Traffic with UP9

Create a New Workspace

Create a new workspace in the UP9 application.

UP9 offers different options for deployment. In this case we'll use Docker, but instructions for other agents are available in the window.


Our UP9 agent is now awaiting traffic.

Run Docker Compose

The following command will create a Docker Compose config file with UP9 agents active.

Change directories to your docker-compose folder and run the following command:

Copy to clipboard
up9 tap:create-docker-compose tutorial-workspace

Here we're naming our new workspace tutorial-workspace, but you can choose something more descriptive for your project. If you'd like to add workflows to an existing workspace, use the name of an existing workspace.

The following command will launch Docker Compose with UP9 agents active. From your terminal, run:

Copy to clipboard
docker-compose -f docker-compose.yml -f docker-compose-up9.yml up -d

Now you have UP9 agents observing traffic in your Docker deployment.

Generate Traffic

Open your project and browse to generate traffic and train UP9. As you browse, you will see a discovery popup, which indicates application traffic is being recorded and sent to UP9 for processing.


You can also run UP9's built-in end-to-end load test with the following command:

docker run --net=host weaveworksdemos/load-test -h localhost -r 100 -c 2

UP9 may ask you to restart services to tap them. To do that in Docker:

docker container restart [OPTIONS] CONTAINER [CONTAINER...]

Once UP9 has enough traffic to understand your workspace, you can begin viewing traffic. UP9 will continue learning your workspace as traffic is generated.

View Traffic with UP9

Open the Traffic tab in UP9 to view traffic flowing across your workspace.

traffic viewer

View Service Dependencies

Select any service to view its dependencies. For example, select the orders.sock-shop service to view its dependencies in a pop-up window.

Services Dependencies

View Requests and Responses

View each request and response as they occur. Here we see a get request for tags at http://catalogue/tags:


And we can view its corresponding response, too:



For support, feel free to use any one of the three: