At this moment, only some JVM and Artemis metrics are exposed , when an Operator based deployment broker is created. But there are no JVM , GC, or thread metrics exposed

Following the ones exposed by default

jvm_buffer_count_buffers
jvm_buffer_memory_used_bytes
jvm_buffer_total_capacity_bytes
jvm_memory_committed_bytes
jvm_memory_max_bytes
jvm_memory_used_bytes

But we want the ones exposed for standalone A-MQ as sawn in ticket ENTMQBR-3573
 
jvm_gc_live_data_size_bytes
jvm_gc_max_data_size_bytes
jvm_gc_memory_allocated_bytes_total
jvm_gc_memory_promoted_bytes_total
jvm_threads_daemon_threads
jvm_threads_live_threads
jvm_threads_peak_threads
jvm_threads_states_threads
In fact, when we make a custom image and add the following configurations on the broker.xml:

<jvm-gc>true</jvm-gc>
<jvm-memory>true</jvm-memory>
<jvm-threads>true</jvm-threads>
the desired metrics are exposed.

But setting a custom image just to expose some metrics, is a bit cumbersome. Could it be enabled on an easier way?