Metrics

JMS Bridge is built on top of ActiveMQ Artemis, and exposes Artemis metrics via Prometheus when enabled.

These metrics are useful for monitoring queue health, message throughput, and system resource usage.

🔧 Prerequisites

Prometheus Agent is already running on JMS Bridge (e.g., http://<bridge-host>:8888/metrics)
Prometheus Server is configured to scrape the bridge

These are helpful to monitor backlog, inflight messages, and delivery health.

Metric	Description
`artemis_queue_message_count`	Current number of messages in the queue
`artemis_queue_messages_added`	Total messages added to the queue
`artemis_queue_delivering_count`	Messages currently being delivered
`artemis_queue_acknowledged`	Total messages acknowledged (consumed)
`artemis_queue_expired`	Total messages expired due to TTL
`artemis_queue_killed`	Total messages removed due to queue full or other conditions

Metric	Description
`artemis_address_count`	Total addresses created
`artemis_queue_count`	Total queues managed by the broker
`artemis_memory_used_bytes`	Broker memory usage
`artemis_disk_store_usage_bytes`	Disk usage by the message store

artemis_queue_message_count{queue="myQueue"} > 1000

Trigger an alert when messages are piling up, indicating possible consumer issues.

increase(artemis_queue_expired[5m]) > 0

Alert when messages are expiring — could indicate delivery delay or consumer issues.

rate(artemis_queue_messages_added[5m])

vs.

rate(artemis_queue_acknowledged[5m])

Compare these to detect imbalance in production vs consumption rate.

artemis_consumer_count < 1

Detect when no consumers are active on a queue/address.

Ensure Prometheus server has the following job:

scrape_configs:
  - job_name: 'jms-bridge'
    static_configs:
      - targets: ['bridge-host:8888']

By using Artemis metrics exposed via Prometheus, you can build dashboards and alerts for: