Currently, we have only one implementation of the TicketingSystem that always reports statistics for both the normal-priority and low-priority pools, and these statistics are cumulative. Here is an example from serverStatus:

queues:
	execution:
		read:
			out: 0, <- this
			available: 100, <- this
			totalTickets: 100, <- this
			exempt:  { ... }
			lowPriority: { 
				out: 0,
				available: 30,
				totalTickets: 30,
				{ ... }
			},
			normalPriority: { 
				out: 0,
				available: 70,
				totalTickets: 70,
				{ ... }
			},
		{ ... }

Reporting the cumulative statistics of low-priority and normal-priority tickets is correct when prioritization is being used. However, it can be misleading when prioritization is not enabled.

It is still beneficial to report statistics from the low-priority pool when prioritization is disabled because the user may change the algorithm at runtime. However, reporting the sum of these statistics at a higher level can be misleading.

One option is to remove the cumulative sum and report only the out, available, and totalTickets values within the respective normalPriority or lowPriority objects.