This is actually kind of easy to do and several ways to do it. SCOM can monitor for an event in SYSLOGS and then automatically open a ticket. You don’t have to use SCOM but rather can use any tool that can watch for an event. I think that you can actually write a script that will trigger against certain events and then can have that script push through the an API to open a ticket.
Alternatively there are BMC tools that can be purchased to not only create an incident but they can also update the actual Asset record with new information. If a monitored service restarts (due to some automation on the box) then it can open a Change ticket instead of an incident and relate that to the asset record. It really all depends upon the end results that you want as to which is the better solution. You can also start with the cheap/ easy solution and then once the company figures out what it actually wants then you can move forward with a more robust tool. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jose Huerta Sent: Tuesday, February 21, 2012 5:44 AM To: arslist@ARSLIST.ORG Subject: Syslog ** Has anyone tried to integrate Remedy with an external monitoring app through syslog? I assume that there is no native support for this kind of integration. But maybe there is some plug-in or commercial app. Regards, Jose Huerta _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
