adapters/

Package command builds with the service's own build.command (ko, bazel, buildpacks, a Makefile, ...).

Package docker builds images with `docker build` and pushes them when the environment has a registry.

Package golang builds a Go main package on this machine and puts the binary on a base image as one layer, with no Docker daemon and no in-container module download: the local build cache makes rebuilds take seconds.

Package redis is the cache adapter for Redis and protocol-compatible servers (Valkey, KeyDB, Dragonfly).

Package sql is the database adapter for SQL servers: one implementation, a dialect per driver (postgres, mssql, mysql) for listing, creating and dropping databases.

Package delve attaches a headless Delve server to a running Go service: to the local process directly, or inside the container (the image needs dlv and the pod SYS_PTRACE) with the port forwarded.

Package ssh manages servers over the system ssh client, so ~/.ssh/config, agents, keys and jump hosts work exactly as they do in a terminal.

Package consul is the KV adapter for Consul's HTTP API.

Package command wraps any load tool behind shell commands: start, stop, rate (with {rate}) and status, whose output may be JSON {"running":..,"rate":..,"sent":..,"failed":..}.

Package http is a built-in open-model load generator: requests go out at a fixed rate whatever the latency (no coordinated omission), from this process, for as long as rig runs.

Package kv drives load generators that run as services and read their rate from a key-value store: the rate is written to a key (or one JSON field of it), start and stop scale the generator services, and counters come from metrics queries when configured.

Package loki reads logs from Grafana Loki: following polls query_range, ad hoc queries take LogQL.

Package runtime serves logs straight from the runtime (kubectl logs, docker logs, local log files), merged across services.

Package kafka reads and manages Kafka through its own protocol: topics with their sizes and the lag of the groups reading them, purge, publish, and queries for groups and the latest records.

Package rabbitmq reads and manages RabbitMQ through its management HTTP API (the management plugin).

Package prometheus reads metrics from anything that serves the Prometheus HTTP API: Prometheus, Thanos, Mimir, VictoriaMetrics, or an OpenTelemetry pipeline that ends in one of them.

Package scrape is a metrics backend with no server: it scrapes the services' Prometheus or OpenTelemetry (Prometheus exporter) endpoints itself, keeps a short in-memory history, and answers a PromQL subset over it.

Package command profiles with any tool you can run: async-profiler for the JVM, perf, py-spy, rbspy, dotnet-trace, ...

Package pprof captures Go profiles from a service's net/http/pprof endpoint, through the runtime's forwarding.

Package http is a query component for HTTP APIs: "GET /path", "POST /path {json}".

Package docker runs each service as labelled containers on one network, so services reach each other by service name.

Package kind is the Kubernetes runtime on a local kind cluster, plus what only kind can do: create and delete the cluster with a local registry, load images, and shell into nodes with docker.

Package kubernetes runs services on a Kubernetes cluster through kubectl, so it uses whatever auth the user's kubeconfig has.

Package local runs services as processes on this machine.

Package jaeger reads traces through the Jaeger query API (Jaeger, or Grafana Tempo's Jaeger-compatible query).

Package tempo reads traces through Grafana Tempo's own API: TraceQL search and OTLP traces.

Package zipkin reads traces through the Zipkin v2 API (Zipkin itself, or anything compatible).