Crash Course Messaging - Interpreting Queue Statistics 

Page / - last modified by Erik Bakker on 2024/02/20 13:45 

Interpreting Queue Statistics 
last modified by Erik Bakker
on 2024/02/20 13:45

Table of Contents

Assessing the health of your queues is critical in a stable and robust integration solution. One of the aspects of determining the health of your queues is looking at the queue statistics. In this Microlearning, we will educate you on the queue statistics overview within the Manage phase of eMagiz.
1. Prerequisites
•	Basic knowledge of the eMagiz platform
2. Key concepts
This microlearning centers around interpreting queue statistics. By interpreting, we mean: Analyzing the patterns based on the information presented to you. With queue statistics, we mean Various information elements on the queue level that will help to understand the health of the queue.
2.1 General interaction principles
All graphs in the Manage phase are created to provide an easy interaction for users to slice the information as needed. Here are some general guidelines for that interaction.
•	Runtime, Queue, and HTTP metrics are sent to the Manage phase every minute, and that interval is runtime specific
•	Logs and error messages are sent instantly to the Manage phase
•	The average value of the last minute of each metric is sent to the Manage phase
•	The graph or the top right menu can select the time dimension. Other graphs will also respond to this selection
•	You can return to the main dashboard via the top right button called "Show Main Dashboard."
•	The main dashboard contains filter options to select specific runtimes or queues
Queue statistics in this format are only shown once you have migrated your JMS runtime to the following generation monitoring stack
3. Interpreting Queue Statistics
Assessing the health of your queues is critical in a stable and robust integration solution. One of the aspects of determining the health of your queues is looking at the queue statistics.
To explain how you can correctly interpret the queue statistics, we will explain the dashboard overview on the queue level. In further microlearnings, we will build on this knowledge by defining the key metrics and the other metrics available on the queue level.
To access the queue statistics overview, navigate to Manage -> Monitoring -> Queue Statistics.
3.1 Dashboard Graphs
When the queue statistics are accessed, the first page shows a dashboard of the queue statistics. An example is mentioned below.

3.1.1 Problematic queues
The problematic queues are displayed top left in the quadrant. Problematic queues are determined by the static alerting setup of the model whereby a value below the threshold of the consumer count or above the threshold of messages in the queue determines whether the queue is in problems or not.

Please note that only the problematic queues are reported here
3.1.2 All queues
In the quadrant below, you can see all queues, the reported consumer count, and the messages in the queue. If there are many runtimes reported, use either the sorting option or the hourglass filter button to find the queue of your interest.

3.1.3 Messages in queue
The message in queue section displays how message traffic is impacted by messages that linger in a queue. When a specific queue shows an unusual pattern in handling messages, the queue graph will reflect this behavior. An example of how this can look is shown below.

3.1.4 Message throughput
This graph shows the message throughput of each queue. With the help of this graph, you can determine how many messages have been processed by a particular queue within a specific timeframe. Effectively this is a clever combination of the messages in the queue graph and the messages added to the queue graph we had on the previous monitoring stack. This eliminates the need to manually calculate this number to gain insights into message throughput when a specific process behaves unexpectedly.

4. Key takeaways
•	There are four dashboard graphs that will help the analysis of a runtime(s)
•	Problematic runtimes are indicated by messages in the queue or an unexpected message throughput.
•	You can best interpret them together as that approach gives you the most context
•	To assist in anomaly detection, use the eMagiz alerting
5. Suggested Additional Readings
If you are interested in this topic and want more information on it, please read the help text provided by eMagiz when executing these actions.
•	1. Prerequisites
•	2. Key concepts
•	2.1 General interaction principles
•	3. Interpreting Queue Statistics
•	3.1 Dashboard Graphs
•	3.1.1 Problematic queues
•	3.1.2 All queues
•	3.1.3 Messages in queue
•	3.1.4 Message throughput
•	4. Key takeaways
•	5. Suggested Additional Readings