Here’s my take on solving this - readme file is tacked on below. I’d be
interested in any feedback or improvements.
// Distributed under Version 2 of the GNU General Public License.
RT Message Broker is meant as a holding ground for incoming messages
from automated sources (HP Openview, for instance) before items become
actual tickets. The NOC’s responisibility is to watch this window and
discard any non-ticketable events or create tickets.
In my environment, HPOV and other automated systems email
firstname.lastname@example.org. The Message Broker logs into the rt-mb IMAP
account and acts simply as a method to bounce real ticketable items to
RT and discard those that aren’t. This has an added benefit of letting
the NOC discard spam before creating tickets.
I acknowledge there may be a better way to do this. This was tossed
together in a couple hours and could stand some improvements.From: “matthew zeier” email@example.com
Sent: Thursday, January 23, 2003 10:36 AM
Subject: [rt-users] feature request or “how to do this”
We have an MSP group that’s using dcl for their ticketing system and one
feature they have that my guys have asked for is a sort of holding queue
tickets to go first before deciding if they are actual ticketable items.
We get a lot of automated alerts to RT (by design) and not all of them
to be ticketable. If there was a way to hold items for the NOC to review
and select which ones to discard and which ones to accept, that’d be
Or perhaps there’s already a way to do this?
matthew zeier | “Nothing in life is to be feared.
InteleNet Communications, Inc. | It is only to be understood.”
(949) 784-7904 | - Marie Curie
rt-users mailing list
Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm