USM and changed source/hostname alarm

Discussion created by Serge on Nov 7, 2012
Latest reply on Oct 23, 2015 by SandroAlves



Here's another interesting discovery I made over USM. We monitor remote hosts via ntevl probe (our own application generates alarms there). So good so far, unfortunately once alarm is risen - actual robot is flagged as having issues instead of a remote host. So here comes pre-processing rules that change source and hostname of the alarm. It works fine, in the alarm console I can see that source and and hostname is changed as it should,


However in USM, the alarm is still listed under originating robot. So it seems that I need to use AO script instead of a pre-processing one.


Anyone else can confirm this?


Thx, Serge.