Once you take into account the comments I make in https://github.com/prometheus/client_java/pull/15/files#diff-e6388528eae512e36bee02774f97d26aR190 about moving the metrics to static attributes of this class and remove the clever ``Map<K,V>`` code, you can take a much more maintainable and less resource heavy approach on the JVM by directly extracting the values from Hysterix and setting them inline in code in ``run()``.

The advantage of doing this is it 1. more clear, 2. less clever (since it does not rely on generated objects to determine code path logic), and 3. because of No. 2 it gives the HotSpot JIT a chance to actually optimize this into machine code if it deems necessary.