Clarification on "Message Count" Metrics in ActiveMQ/Destination Dashboard

[vishalkadam18]

Hi Team,

I noticed that under ActiveMQ/Destination, the "Message Count" metric appears to aggregate data from multiple underlying metrics.

Could you please clarify which specific metrics are being used in the "Message Count" visualization? For example, does it include Enqueue Count, Dequeue Count, Dispatch Count, Expired Count, In-Flight Count, or a combination of these?

Thanks for your support and for the great tool!

Best regards,
vishal kadam

[wu-sheng]

It includes multiple metrics. You could see this in the dashboard configuration.

[vishalkadam18]

Yes, there are multiple metrics, but could you confirm which data is being shown in the message count on the dashboard?

We are using five different metrics as shown in the picture, but I believe only one metric's data is being displayed.

Can you guide me on which data is actually shown in the picture?

[wu-sheng]

The metrics are from

skywalking/oap-server/server-starter/src/main/resources/otel-rules/activemq/activemq-destination.yaml

Lines 53 to 64 in 4609050

	# The number of messages sent to the destination.
	- name: enqueue_count
	exp: org_apache_activemq_Broker_EnqueueCount.sum(['cluster','destinationName','destinationType'])
	# The number of messages the destination has delivered to consumers.
	- name: dequeue_count
	exp: org_apache_activemq_Broker_DequeueCount.sum(['cluster','destinationName','destinationType'])
	# The average time a message was held on this destination.
	- name: average_enqueue_time
	exp: org_apache_activemq_Broker_AverageEnqueueTime.sum(['cluster','destinationName','destinationType'])
	# The max time a message was held on this destination.
	- name: max_enqueue_time
	exp: org_apache_activemq_Broker_MaxEnqueueTime.sum(['cluster','destinationName','destinationType'])

I do a little digging, it seems this is a UI layout bug. It should be multiple lines. We will fix it.

[wu-sheng]

Tracked from #13201

[vishalkadam18]

@wu-sheng can i fixed it??

[wu-sheng]

It is a UI bug. You need to combine the metric name(or label in UI config) with labels of the metric response.

I am not sure whether you are familiar with this.

[wu-sheng]

We already have a fix here, apache/skywalking-booster-ui#467