From the course: DevOps Foundations: Distributed Tracing

Testing the setup

From the course: DevOps Foundations: Distributed Tracing

Start my 1-month free trial

Testing the setup

“

- [Instructor] Let's open the starter project in Eclipse from the exercise files. I already have imported my project, but if you haven't done that recently, here's the steps. So we go to file, we'll say import, then we'll pick a existing Maven project, and then here we'll navigate to where you place the exercise files on your local machine. So in this case, let's see I have things running on my desktop. Here's the trace lab, and we'll say open, and this will automatically give you the import option for this lab. So once you import the project, so you have access to all the sources, and again throughout the lab we will be making changes here, kind of incrementally building our lab, and testing different instrumentation techniques. Next, I'll go to a terminal window to start the Zipkin and Jaeger backends. But before that, since I'll start with Jaeger, we need to make sure that your Docker daemon is running, so we'll get that started first. So go to your Applications directory, and again providing that you've already installed Docker, I'll just start a daemon here. Okay, Docker is running. So I'm going to download the Jaeger container and run it. Now this may take a few seconds, depending on your connection. Okay, it's downloaded. And now, I'm going to run that all in one Docker-based Jaeger server backend. What I'm doing here is there's some internal port mapping that are set up when we start a container. And again, I'm going to specify the container image next that we just downloaded. And if I've done everything right, we should be good to go with Jaeger. I missed the dash. There we go. So we have our Docker container running for Jaeger. Next, I'm going to switch a terminal window, and I'm going to start Zipkin, so you get a sense of how to get it started. Okay, I'm in the Zipkin folder. And first, I'll fetch the Zipkin start up script, https... okay. So this should download the script. Okay, and I'll pipe it into quickstart.sh. Next, I'm going to run the script. So this will actually download the binaries for Zipkin. And now, we have all parts of our lab ready.

Contents