Author |
Message
|
zpat |
Posted: Tue Apr 21, 2009 2:36 am Post subject: Statistics messages - do they need housekeeping? |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
If I enable queue statistics at the QMGR level (to medium) on a fairly low volume queue manager (say 10000 messages per day over 10 queues) - is there a need to housekeep the statistics queue?
What about channel statistics? I am not worried about the performance overhead on the queue manager, but I don't want statistics queues filling up. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Apr 21, 2009 3:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Uh... What's the point of enabling statistics if you aren't going to actually collect them?
Stats messages should be consumed by your monitoring tools and the relevant data in them digested and stored however your monitoring tools keep stats history (usually in a database...) |
|
Back to top |
|
 |
zpat |
Posted: Tue Apr 21, 2009 4:13 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
I was just wondering whether these messages were consumed or just updated on the queue (OK technically get and put a new message).
So are you saying that MO71 or MQ explorer actually consumes the queue statistics messages?
I don't think it does since I can re-start the MO71 program and see the exact same queue statistics.
The point of enabling them is to have available when needed, even if the queue manager is not regularly monitored (eg development levels).
Many sites don't have MQ system management tools.
I would like to understand how this feature actually works, but I can't see much detail in the "monitoring MQ" manual. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Apr 21, 2009 4:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
A simple test will tell you if the messages are overwritten or not.
Get the current queue depth, and if you like the the oldest message age. Run RESET QMGR TYPE(STATISTICS). See if the qdepth doubles or not and if the oldest message age changes or not.
... I forget whether they're overwritten or not, thinking about it I believe they are. Regardless, the messages produced are only ever going to cover a single STATINT period. So if you need any kind of historical reporting, you need to store this information somewhere. And I know for a fact that MQExplorer does *not* do this, even if M071 might.
I'm well aware of how few shops are able to show proper business justification for tracking the performance of their middleware and for using enterprise caliber tools to manage the enterprise. |
|
Back to top |
|
 |
zpat |
Posted: Tue Apr 21, 2009 4:49 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
My aim is just to have some simple current period statistics for development queue managers which would otherwise have none.
I am not trying to make this production strength, but I don't want to enable anything that needs housekeeping (on development boxes).
Sounds like queue statistics is a case in point, no housekeeping needed, so may as well enable it everywhere.
Still not sure about channel statistics. |
|
Back to top |
|
 |
Sam Uppu |
Posted: Tue Apr 21, 2009 7:47 am Post subject: Re: Statistics messages - do they need housekeeping? |
|
|
 Yatiri
Joined: 11 Nov 2008 Posts: 610
|
In my development environments, I turned on the STATQ(ON) for the queues which needed the stats info.
Since couple of months I didn't turn off the statq. Still I see around 46 messages on this SYSTEM.ADMIN.STATISTICS.QUEUE queue and there is no monitoring tool listening on this queue.
The stats will be turned off in PROD but need to know whether this queue ever fills up as its maxdepth is 3000(default) and the STATINT(1800) which is half hour(default) is on QMgr if the stats are turned on.
Thanks. |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Apr 21, 2009 8:09 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
The MQ product doesn't include apps to consume messages sent to the instrumentation event queues.
So, the messages will continue to accumulate until you take some action. Besides running an app, you choices include: put(disable) the queues, or turn off monitoring, or clear (MQSC) the queue(s). _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
SAFraser |
Posted: Thu Apr 23, 2009 12:07 pm Post subject: |
|
|
 Shaman
Joined: 22 Oct 2003 Posts: 742 Location: Austin, Texas, USA
|
zpat, I understand your question and I have the same question.
We use a third party monitoring tool. Just as in MQExplorer, for my third-party tool I must turn on stats in order to see last put date/time and last get date/time. This is real-time/runtime data that we use in both development and production daily. But the tool collects lots of history without stats turned on; so, I am not entirely clear on how stats work.
(And yes, of course, we also use the historical data collected by our monitoring tool. We use both runtime and history.)
The stats queue fills up all the time. I've wondered about housekeeping. Now I wonder if they are circular. bruce2359, do you know for a fact that these messages are not overwritten? Because I'm not sure a full queue stops the data collection.
zpat, when I find a minute, I'll try mqjeff's test. If you try it first, let me know what you learn. Thanks! |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Apr 23, 2009 1:32 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
The instrumentation queues are queues. They fill up like other queues. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
|