Tracetest in Action: Running Trace-Based Tests on the OpenTelemetry Demo App with Nomad

1

Open Telemetry

Back in 2018, Trace-based testing was just an idea. Fast-forward to today: TBT is now a reality, thanks to Trace standardization à la OpenTelemetry (OTel) and Trace-based testing tools like Tracetest, Helios, and Malabi.

#Monitoring Tools #Performance Monitoring #Log Management 156 social mentions

2

Nomad Project

In this section, we’ll be provisioning a local Hashi environment (including Nomad, Consul, and Vault) instance using HashiQube. Then, we’ll install Tracetest and the OTel Demo App on Nomad. Feel free to skip this section if you already have a working Hashi environment with Nomad, Consul, and Vault.

#Developer Tools #DevOps Tools #Containers As A Service 8 social mentions

3

gRPC

I’m a big fan of doing things programmatically, so let’s create our test from a YAML file. Per the Tracetest docs, you can create tests from HTTP requests, gRPC requests, cURL commands, and more. In our case, we’re creating our tests from a gRPC request, so our Tracetest test definition file YAML looks like this:.

#Web Servers #Web And Application Servers #Load Balancer / Reverse Proxy 86 social mentions

4

Docker

Docker (version 20.10.21 at the time of this writing) - we’ll be running HashiQube on Docker, using the Vagrant Docker Provider.

#Developer Tools #Containers As A Service #Container Tools 62 social mentions

5

cURL

I’m a big fan of doing things programmatically, so let’s create our test from a YAML file. Per the Tracetest docs, you can create tests from HTTP requests, gRPC requests, cURL commands, and more. In our case, we’re creating our tests from a gRPC request, so our Tracetest test definition file YAML looks like this:.

#API Tools #APIs #Developer Tools 105 social mentions

6

Consul

Is the address at which the gRPC endpoint is served. In this case, we’re using Consul DNS to expose the service’s address. If we look at the Recommendation Service’s Nomad jobspec, you’ll see that the name of the gRPC service is recommendationservice. So when we query it in Consul, it should be accessible at this address recommendationservice.service.consul. We can test this by logging into the HashiQube image. Do this by going to the root directory of HashiQube repo, and typing vagrant ssh. Once you’re in the HashiQube Vagrant box, run this command:.

#Help Desk #IT Management #Service Desk 6 social mentions