Onfault's - What is everyone doing with their error & status reporting?

[BurmJohn]

I am in the process of finishing up my core error reporting and status
reporting BP's that I'll be using in all of my BP's. Just curious
what everyone else is doing with theirs? I am logging mine to a
database so I have a quick way to check if something failed. Another
reason for doing this is so in the future (when time allows) I'll make
a quick status web page and or app where I can see the last few errors.
I had envisioned the app as being a windows based app where it would
check the error DB and give me a quick popup notification on my
desktop and our computer room's peoples desktops. I also have a
status reporting BP that does the same as the error, however it
reports when a BP has run and time stamp and the fact that it was
successful (its at the end of the BP's). Just trying to get some
good idea's, let me know what you guys think.

Thanks

[hmbp]

We have them send emails to us, in the case of errors. Although, I couldnt shed much light on how that is done exactly, since the BPs that do that were already written when I got here. I just create my BP and set my OnFault to call the email BP in case of errors.

[zmikez]

We use Altiris Helpdesk. I have the BP email a special exchange account that altiris picks up and then altiris emails the group. It works really well except for very large documents as it puts the document in the body of the email by default. I have a project on my round-to-it list to use the altris webservice but it's horrible. I think it was writer of the webservice last built a web app in 98.
The best reason for using a ticketing system is that errors don't get lost, plus you can do some cool statistical analysis.

[BurmJohn]

Mike,

What if you sent the error as an attachment rather then in the body? I havent gotten around to do that yet, however that's my goal. In addition to logging the error to a table on our sql database.

[zmikez]

That's what I'm working on right now. Trouble is, I've given the PrimaryDocument a name (GetDocInfo) and moved it to Document. I've piped the StatusRpt to Status_Report but I can't name it. GetDocInfo wants the DOCIMENT_ID for anything that's not PrimaryDocument. According to the documentation, this is the text portion of the attribute SCIObjectID but it doesn't like it. I have a case open but it's SLOOOOOW to get any real info out of Sterling.

[BurmJohn]

I hear you! Let us know once they get back to you.

My goal is to create a someone open source status reporting bp for everyone to contribute to, hopefully we can get a few of us brainstorming. I had posted a thread to get the discussions started.