Hi,
I just wanted to clarify a few questions I have running around in my little head since im facing an upgrade form a large MOM2005 to OpsMgr 2007.
What we have today is:
Selected alerts have been assigned a custom Alert resolution state which means that the alert should be picked up and handled by our ticketing system.
Our ticketing systems then looks in the Onepoint DB and finds all alerts with our custom resolution state, after the ticketing system picked up the alert it changes the resolution state again indicating that the alert is picked up and is now active in our ticketing system.
When the ticket is closed it also closes the alert in MOM.
Is this going to be a "valid" solution in OpsMgr as well? Since this is a very "friendly" way to integrate mom with ticketing systems if you know a bit of SQL it has been our preferred way of doing things.
It also makes it very easy for us to define which alerts we want forwarded to our ticketing system.
Basicly im not even in the test phase of OpsMgr yet, still waiting for the new blade servers to run it on, this also means that I havent digged into the new DB layout of 2007 yet.
But how have you guys gone about doing this, im open to all suggestions just want some idea's :D
I will also try to make a generic solution available if people are interested, with loads of integrations done in 2005 im not afraid of playing around with all OpsMgr has to offer behind the scenes as well.
Søren Larsen, Systems Engineer at Danfoss A/S.
Mostly working with monitoring, I do some devolping for mom, some of it you can find on this site. ;-)
Pretty active on the public mom newsgroups also.