I am trying to find problems created by imaged systems running Alertus software.
Scenario:
Client checks into Alertus and logs its hostname while application assigns it a deviceID. Techs deploy Image that had Alertus previously installed. Newly imaged systems checkin and Alertus Application thinks its same device so it adds system with same deviceID but with different hostname. Causing repeated check-ins with new hostname and IP change.
I want to be able to find and alert on the following
Ignore event
Event1: field1=0077C1, field2=frontofficePC
Event2: field1=0077C1, field2=frontofficePC
Alert on this (0077C1 belongs to frontofficePC)
Event3: field1=0077C1, field2=backofficePC
sample log
2017-05-15 11:54:34.046 [INFO] 0077C1 (51504) [backofficePC\user1] - Auto-update flagged: Reason = IP address changed from 10.13.8.15, 172.24.139.192 to 172.24.139.192
Please and thank you for any help or direction.
... View more