hashiqube VS tracetest

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.

I run Nomad locally using HashiQube.

We used HashiQube to stand up a local HashiCorp environment in Docker via Nomad so that we could run the OTel Demo App in Nomad using Traefik as our load balancer.

Code Example

Also, please feel free to join our Slack Community, give Tracetest a star on GitHub, or schedule a time to chat 1:1.

Feel free to connect with us on social media, join our Slack community, and give us a ⭐ on GitHub.

git clone https://github.com/kubeshop/tracetest cd tracetest/examples/setup-of-tracetest-tests

The code to execute this scenario is contained in the delete_test.ts file from a repo which we will clone and run locally further in this article. First, let’s discuss the code for the key sections that are utilizing the [@tracetest/client](https://www.npmjs.com/package/@tracetest/client) NPM package.

If you want to see the code example right away, check it out on GitHub, here.

If you’re eager to start, clone the example from GitHub and get a Tracetest Agent public URL and Token after signing up at app.tracetest.io. Sign up for a Cloudflare account on

For this example, I’ll showcase this simple example app for Tracetest and Sumo Logic. To quickly access the example, you can run the following:

If you get stuck along the tutorial, feel free to check out the example app in the GitHub repo, here.

It’s official! You can now use synthetic monitoring to run trace-based tests with Tracetest’s new GitHub Action. I’ve already implemented dogfooding and it’s currently running in production as health checks, running hourly, here.