| Author |
Message
|
| tminifie |
 Posted: Fri Sep 26, 2008 7:37 am Post subject: Dead Letter Queue monitoring |
 |
|
Apprentice
Joined: 18 Jan 2007
Posts: 26
|
I need to develop a script to monitor our CORE_DEAD_LETTER(DEAD_LETTER_QUEUE) queue, more specifically to email a list of people every time a message lands on this queue. I have some experience with MQ and I know that I could create a simple script that polls the queue every few sec/mins and sends off an email if the queue depth is greater than the depth during the previous poll. However, I don’t know that this is a good approach; any suggestions on how I could approach this? Perhaps MQ already has built in capability to do this?
We are using MQ v5.3 and v6.0.
Thanks,
Todd |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Sep 26, 2008 7:38 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
What is your company's Monitoring solution? I'm sure it has an MQ component. I hope anyway. You should avoid reinventing this wheel.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Sep 26, 2008 7:48 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I suppose it would be possible to trigger a program on message depth for the DLQ.
Then the program could be very simple and not have to "poll" the queue at all. |
|
| Back to top |
|
|
| tminifie |
| Posted: Fri Sep 26, 2008 7:48 am Post subject: |
|
|
Apprentice
Joined: 18 Jan 2007
Posts: 26
|
| yes we are using SiteScope, but I am told by our administrator that the way it is currenlty configured, an AR Remedy ticket is opened every time a queue threshhold is hit and that is fine for all the other queues that we are currently monitoring but we don't want this to be the case for our dead letter queue monitoring. I don't know if this is a configuration limitation or a political issue so I am trying to come up with an alternative.... |
|
| Back to top |
|
|
| jeevan |
| Posted: Fri Sep 26, 2008 8:30 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| tminifie wrote: |
| yes we are using SiteScope, but I am told by our administrator that the way it is currenlty configured, an AR Remedy ticket is opened every time a queue threshhold is hit and that is fine for all the other queues that we are currently monitoring but we don't want this to be the case for our dead letter queue monitoring. I don't know if this is a configuration limitation or a political issue so I am trying to come up with an alternative.... |
Each queue has it own requirement for monitoring and alerting. So, I do not think it is a problem. Eg. we use patrol. In regular queue, we raise an alert once the number of message riches a certain number but for a dlq, we raise an alert once it has a message.
You should not reinvent a wheel if there is not politics involved. If you can not use for tools for monitoring which is not for problem ticket, you can can simple perl script, poll for the queue, once it has a message, email a group of people you would like. I am not sure, you even can do this simply in unix sheel. |
|
| Back to top |
|
|
| tminifie |
| Posted: Fri Sep 26, 2008 9:23 am Post subject: |
|
|
Apprentice
Joined: 18 Jan 2007
Posts: 26
|
Thanks for the response Fella's.
I will go back to our administrator and if its company policy to always open an AR ticket when SiteScope queue monitoring is alerted then I will put a trigger on all of our dead letter queues to call a unix shell script that will send email notification. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Sep 26, 2008 10:01 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Application developers need to specify what should be done with messages that end up in your DLQ instead of the intended application queue. Emailing someone that this has happened is part of the solution.
IBM provides RUNMQDLQ, the dead-letter queue handler utlity. You can/should write a script (refer to the WMQ System Admin manual) that processes these dead messages out of the DLQ so it doesn't fill up and cause the channel to stop.
For example, if the message ended up in the DLQ because the destination queue was (briefly) full, the dead-letter handler can try again to put the message in the same (or different) destination queue.
_________________
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 |
|
|
| tminifie |
| Posted: Fri Sep 26, 2008 10:35 am Post subject: |
|
|
Apprentice
Joined: 18 Jan 2007
Posts: 26
|
| point taken, Thanks Bruce! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Sep 26, 2008 9:00 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Keep also in mind that the message in the DLQ might be transitory (set to expire). So depending on your business needs it might be a good practice to only send the email/page after the message(s) have been in the DLQ for more than x minutes. This way you don't logon and go to the DLQ only to find that there is no message there because it has expired....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
