nomad-conversions VS malabi

Please note that there are no official Nomad jobspecs for either Tracetest or the OTel Demo App, so I went ahead and did the conversions myself from Kubernetes manifests to Nomad jobspecs. You can check out the jobspecs in this repo. If you’re curious as to how I went about the Kubernetes-to-Nomad conversion, you can check out my blog post on this topic. I also have a blog post dedicated to running the OTel Demo App on Nomad. If this tickles your fancy, you can check it out here.

NOTE: You can find the repo with all of the OpenTelemetry Demo App jobspec files here.

git clone https://github.com/avillela/nomad-conversions.git cd nomad-conversions

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.

Malabi is an open-source test framework. With Malabi, you can write integration tests on distributed systems by collecting data from a microservice during a test run, then exposing an endpoint to make assertions on that data. The maintainers say Malabi implements trace-based testing, similar to Tracetest. Malabi uses OpenTelemetry to collect your trace data.

This use case is exactly what has led to the creation of Malabi, an open-source that wraps the OpenTelemetry SDK and does all this setup for you so that you can simply add it to your project and start asserting.

Malabi is still in its early days, so if you find it interesting, feel free to help in any way (contribute code, knowledge, or ideas). https://github.com/aspecto-io/malabi ⭐️