This is default behavior whenever the threshold breach alarm will be generated by rate, and for this alarm any change in value it will matches with thresholds and accordingly new event will create/closed against the original alarm.
So alarm ID will be same and event ID it will keep changing based on state change.
My answer would be not possible in terms of flow through rate.Also would like to understand business use case for such requirement.
Thans for your response.
Requirement is to get two different Event so that we get two different Remedy Tickets.
We would like to have two individual tickets created in remedy for both Minor and Major alerts.
If creation of seperate Events is not possible in BPPM can we have a new ticket created in remedy for Major Threshold?
1 of 1 people found this helpful
If you know some MRL programming, the solution is actually straight forward.
You can write a rule in execute phase to 'catch' this type of events whenever their severity changes. In your rule, simply call generate_event() to generate a new event with all the slots you need for Remedy ticketing copied from the original event. Your new event can be the same class as the original one or you can define a new class name. I prefer a new class name because it makes specifying ticketing criteria easier. If you use the same event class for your new event, you need to set a flag in an event slot so that only the events with the flag set will get tickets created. The original events will never get tickets created.
BPPM JServer is the only event source that directly updates and closes the events in cell. All other event sources only send events to the cell but never update or close the events. Whether or not those events should be updated or closed is up to the cell (based on its MRL rules or policies) to decide. I had to use similar method to 'catch' BPPM Jserver events and change this default behavior so that I can use one set of rules to process events from 8 different event sources.
Hope it helps,
Thanks a lot. It was very helpful. I will try this option.
I believe Willa's suggestion is good option to try.
I would just to add that the Remedy ticket opened by the original event should be opened only when the severity reaches the higher level (so please review you ticket creation policy).
In other words, if my metric breaches the minor threshold and then the critical threshold you should have:
1) Minor --> create new event --> open ticket for that new event
2) Critical --> open ticket for the original event
I hope it helps.