ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ API Support » Reporting the depth of a queue (& other interesting stuf

Post new topic  Reply to topic Goto page Previous  1, 2
 Reporting the depth of a queue (& other interesting stuf « View previous topic :: View next topic » 
Author Message
jcalderone
PostPosted: Wed Nov 04, 2009 11:56 am    Post subject: Reply with quote

Novice

Joined: 02 Nov 2009
Posts: 12

bruce2359 wrote:
As an exercise: if you inquire on currepth of a queue, and discover that curdepth is 5, what will you do with this information? Or, more accurately, what will those that requested this type of information learn from the fact that curdepth is 5?

What does it means when curdepth is 5?


I won't do anything with it. The people in charge of monitoring expressed an interest in it. I didn't ask what they would do with it. I assume they'll use it to try to smooth out load spikes, improve load balancing, notice points of failure, increase server utilization, or something else along those lines. That's just me, though - like I said, I didn't ask.
Back to top
View user's profile Send private message
jcalderone
PostPosted: Wed Nov 04, 2009 12:00 pm    Post subject: Reply with quote

Novice

Joined: 02 Nov 2009
Posts: 12

Vitor wrote:
jcalderone wrote:
So, for example, is there an existing tool like this which can report the current depth of a queue? Even better would be something that could report on many or all of the other stats about queues and queue managers (enqueue count, high queue depth, queue empty, etc).


You've just described every commercial monitoring tool with WMQ capabilities! These are (as I'm sure you've discovered) the common things which need to be monitored and possibly acted on.

Another viable plan is to ask your local admins what they're using to monitor CPU, RAM, disc space and so forth. Most of those monitoring tools have WMQ capability.


Apologies for being a bit unclear. I'm not surprised to learn that these are things monitored by every commercial monitoring tool with WMQ capabilities. However, there is already a monitoring system in place here which does not support WMQ. The task is to give this system some WMQ support. I think it will be satisfactory to do so by re-using some existing tool, but the tool does need to be able to be integrated into the existing system; a wholesale replacement monitoring system with WMQ support isn't going to fit.

Vitor wrote:

You could do a lot worse than look through the "Monitoring and tools" section of this forum. Most of the software "usual suspects" have been discussed at one time or another.


Cool. I thought I'd looked over all the sections already, but I missed this one. I'll go look through the postings there now. Thanks!
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Nov 04, 2009 1:09 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

If the COTS monitor *really* doesn't have a WMQ component, then you are still probably much better off buying a real WMQ component, and configuring it to output alerts into a format that the COTS software can pick up.

If, for example, the COTS software can read a process a text file, you can configure almost all WMQ software to write out a formatted text message when the WMQ monitors detects a given situation.

It's a bit like phoning a friend to have him pass a note to your buddy, but it's still probably represents a better VALUE.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Nov 04, 2009 2:29 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

Quote:
there is already a monitoring system in place here

May I ask which monitoring system?
_________________
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
View user's profile Send private message
jcalderone
PostPosted: Thu Nov 05, 2009 6:16 am    Post subject: Reply with quote

Novice

Joined: 02 Nov 2009
Posts: 12

bruce2359 wrote:
Quote:
there is already a monitoring system in place here

May I ask which monitoring system?


Sure: Zenoss
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » IBM MQ API Support » Reporting the depth of a queue (& other interesting stuf
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.