11-11-2013 11:47 PM
Is it possible to achive this behavior in BSM?
It's like Service Tree works in HP Operations Manager - Service status is (by default) equals the worst status of events assigned to it.
In BSM event-based HI's status equals to severity of the LAST event assigned to it (useless).
Solved! Go to Solution.
11-12-2013 05:55 AM
this is not correct. The unassigned/unresolved KPIs will display the status of the worst open event assigned to the CI.
if your event will have ETI to impact HI, then the last event will control the HI status. if you will send "SubCiHint" with your events, to impact the same HI (for example: CPU Load HI, but with SubCIHint=CPU1 and CPU2) then the HI Status will be the worst of all SubCiHints and each is calculated individually (so for example if CPU1 got clear event and CPU2 is still Critical, then the HI will show Critical).
11-12-2013 10:25 PM
Asaf, this is exactly what I needed. Tested - works great.
Shame on me - this is described in documentation, though not in great detail.