All these metrics, except publishers & consumers, are handled by
rabbitmq_global_metrics, so we currently have duplicates. As I started
removing these, I realised that tests were written in Java - why not
Erlang? - and they seemed way too complicated for what was needed. After
the new rabbitmq_global_metrics, we are left with 2 metrics, and all the
extra code simply doesn't justify them. I am proposing that we add them to
rabbit_global_counters as gauges. Let's discuss @dcorbacho @acogoluegnes
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
For mysterious reasons, it turns out that using rabbit_ct_helpers:exec
with the `[binary]` option cause `aws ec2 describe-instances ...` to
fail with "bad argument". Removing the option and using
`list_to_binary/1` on the response before json parsing seems to
alleviate the issue.
Also make RABBITMQ_IMAGE non-optional for integration_SUITE
Adds WORKSPACE.bazel, BUILD.bazel & *.bzl files for partial build & test with Bazel. Introduces a build-time dependency on https://github.com/rabbitmq/bazel-erlang