* Move `jsonnetfmt` and `goimports` install into tools/
This will ensure that the version we are using to compile locally is the
same version that we are using in CI. The `goimports` was already
included in the tools, and so the CI was redundant. Also not, this
moves us from the C jsonnet to the Go jsonnet, which looks to introduce
slight formatting changes.
* Compile jsonnet
* Move tk, jb, and jsonnet also into tools/
* Include tools dependency on additional make targets
* Include tools Dockerfile
* Include tools image build target
* Update tools/go.sum
* Tidy up image build
* Prepare multi-arch docker image with install script
The script is used because not all imports in the tools.go are modules
which can be imported. The version of the import is determined by
matching the nearest module path and installing the import at the
version specified in the go.mod. This will allow updates to the go.mod
to direct the versions of the tools installed in the docker image.
* Stop ignoring the tools to allow docker build
* Include entrypoint
* Use TOOLS_CMD for docker execution on a few key make targets
* Use my image
* Fix variable
* Mark workdir as git safe
* Update drone to publish a tempo-ci-tools image
* Fix --platform for image source and use golang:alpine
We also ingest data through the internal gateway now.
Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>
Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>
* Filter namespace by cluster in tempo dashboards variables
* Update CHANGELOG.md
* run jsonnetfmt
* Use same jsonnet version and implementation as CI to make CI happy
* Adjust write panel in operational datashboard
Here we aggregate the data on on the write tab by cluster.
sum by(cluster) (rate(tempo_ingester_traces_created_total{cluster="$cluster", namespace="$namespace"}[$__rate_interval]))
sum by(cluster) (rate(tempo_distributor_spans_received_total{cluster="$cluster", namespace="$namespace"}[$__rate_interval]))
* Compile tempo-mixin
