How to use KEDA to scale ActiveMQ Artemis (Operator-managed, StatefulSet) using connection count & other metrics (Jolokia disabled)

[akshay1092]

Hello Team,

We run ActiveMQ Artemis on Kubernetes using the Operator (StatefulSet brokers). We want to use KEDA for autoscaling and would like to trigger scaling not only on queue depth but also on connection count and possibly other broker metrics (e.g., consumers/producers per address/queue, message rates, etc.).

Constraint: We have Jolokia disabled for security reasons, so solutions relying on Jolokia/JMX are not an option.

Environment & context

• ActiveMQ Artemis: deployed via the official Operator

• Deployment: Brokers are in a StatefulSet

• Autoscaling: Want to use KEDA ScaledObjects

• Metrics desired for triggers:

  • Queue size (per queue or per address pattern)

  • Connection count (total or per broker)

  • Potentially consumers/producers per queue, enqueue/dequeue rates, etc.

• Security: Jolokia endpoint is disabled

• We tried to explore the Scaler Artemis with triggers type as artemis-queue : Does this works only with queueLength or any other metrics also ? And the parameter 'restApiTemplate' uses jolokia to query the mertrics ?

• We are exposing the metrics on https://broker-service:8161/metrics/ can this made use by artemis-queue?

• By default will have 2 replicas for the brokers, will there is aggregated metrics from all the pods or it has to be configured for individual pod?

Regards,
Akshaykumar