The phantom scala driver wraps the ClusterBuilder to produce a final version of a cluster that generates the end session.
The link in question is here, where the final cluster produced is produced with a function from ClusterBuilder => ClusterBuilder which allows the user to provide their own options, after which we are as an expertiment actively forcing .withoutJMXReporting().withoutMetrics() on the final builder object.
Even with this forced behaviour, the following still occurs:
Why are metrics settings completely disregarded by the builder? Shouldn't they be disabled at this point? This seems to be a new issue found in 2.2.0-rc3