I am looking for guidance on setting up a queue to the emailgtw probe, so it is protected from restarts and we can see the backlog. Has anyone done this if so how?
I think you just have to create an attach queue on your hub with a name of emailgtw. Configure it to get all messages with a subject of EMAIL.
If I recall correctly, the emailgtw probe will attempt to connect to a queue named emailgtw when it starts. If that fails, it will subscribe to all messages with a subject of EMAIL (which is what usually happens).
Worked like a charm
I do not know of a way to view messages in a queue on a hub. You can "sniff" the messages as they pass through the hub (in the hub GUI and in the DrNimBUS tool), but once they are in a queue I do not think you can inspect them.
If you want to know what email went out, I think you would have to rely on the emailgtw.log file for that. I do not think the emailgtw keeps a status list or anything like that. You will have to see if you can find an appropriate loglevel for the emailgtw that shows you the right amount of detail without filling the log with information that is useless to you.
We also set up an email account that everything is cc tom just so we have an official record. We store past messages fro 45 days. Then if a customer needs proof we can research alarms in the nas history and attach the correlating email from the email account. I realize that was not exactly what you were looking for, but another option that may be of use.
The way we are starting to do emails is using a LUA script. Within the AO Profile we used to choose EMAIL but there was no log of what alarm went to who to reference. So, we are changing the AO to script option and using the script arguments to pass the email addresses and email groups and within the script we log all the pertinent information about the alarm and the email address we sent to along with attaching a note to the alarm specifying an email was sent.
I would prefer that there be a simple way to know what emails were sent out. But, I can work around this I guess. It is the job of our help desk software to log and track all email communications with our customers. And Nimsoft is integrated into our Service Desk.
We actually do it the way Jarrod does as well this way the alarm transaction is logged saying it ran the email script we then auto assign it as well.
Retrieving data ...