Hi listers, I have a problem that is forcing me to develop a lot of code. I'm sure that there is an easier way to solve it, so I call for your knowledge about it. Surely I'm not the first to face this situation.
I have a monitoring tool that send events to ARS when some situations are found. The event is received through a Web service that stores the event in a custom form. We have a lot of code to process this event, to determine if we need to create an incident, a comment, change something, ... One of the possible events is the detection of a CI unavailable. Then my code checks the status of the CI at the CMDB, to see if it is unavailable for some reason (like a planned shutdown or an end-of-life). If it is marked as available, then we need to start an unavailability request, and create a related incident. Using the HPD:Help Desk form is like creating a new incident, relate it to the CI and go to the relationships tab, quick actions and create an unavailability record. But I see that most of the code used to process this situation is at the Active Link side, so I can't use it from my custom form. I started to reproduce all the code so at the end I will finish with: - The CI avalability status = "Down" - The CI has an unavailabilty request. The assignment method is crossed reference. - A new incident is created related to the CI and the unavailability request. I getting mad with the amount of code to be created. Any of you have an easier solution? The rationale behind this is that we want to capture the availability status of CI's, in order to control them through the SLM; and we want to warm the support staff so they can solve the unavailability as soon as possible. May be my approach is not the best. What's your opinion? Regards, Jose Manuel Huerta http://theremedyforit.com/ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
