Can some one tell me whether any log will be generated when a new agent is installed and attached to the hub in CA UIM.
If the new robot is visible / registered in IM
Depending on hub update interval for each target robot
Setup->Misc->Hub update interval(in minutes)
You can see below robot heartbeat messages in the related hub at loglevel 3
For working robot=================
Line 91416: Jan 2 09:23:28:989  hub: alive - dsofr01-i24xx 10.131.236.*** (s:101) Line 92228: Jan 2 09:24:28:995  hub: alive - dsofr01-i2434 10.131.236.*** (s:101) Line 93015: Jan 2 09:25:28:994  hub: alive - dsofr01-i2434 10.131.236.*** (s:101) Line 93789: Jan 2 09:26:28:992  hub: alive - dsofr01-i2434 10.131.236.*** (s:101)
For registered robot not working===============================
Line 6: Jan 2 07:34:30:202  hub: internal alarm - Robot dsofr01-e60xx is inactive, 5, dsofr01-e60xx Line 6: Jan 2 07:34:30:202  hub: internal alarm - Robot dsofr01-e60xx is inactive, 5, dsofr01-e60xx Line 7: Jan 2 07:34:30:202  hub: heartfailure - dsofr01-e60xx is dead
In our environment multiple teams are installing Nimsoft agent in the servers which will cause some servers to be missed and not adding required probes for monitoring. In order to avoid this we thought of setting up some notification when a new agent is added in to the UIM domain. Thats why I asked for any log files(like windows event log) which will be generated when a anew agent is added.
Installing windows robot installs a new nimsoft robot watcher service if you check with services.msc
Please check if these events are logged/enabled by your Windows system event logs
It is accepted that by 'Nimsoft agent' the intended meaning is installing a robot. This can be done via a local installer, in which case the install log will be local to that system.
It may be asking too much but at least to me the obvious is to expect some level or responsibility from whoever is installing a new robot to notify you.
If that is unrealistic then the table CM_NIMBUS_ROBOT can be queried. When the count goes up a new robot has been added. Perhaps a custom checkpoint can be added to the appropriate database probe to do that.
Also see this prior thread on this subject.
New Robot Notification
Check up CM_NIMBUS_ROBOT table is a good approach.
Here is an example of CM_NIMBUS_ROBOT and CM_NIMBUS_PROBE combined.
from CM_NIMBUS_PROBE cmnp
INNER JOIN CM_NIMBUS_ROBOT cmnr on cmnr.robot_id = cmnp.robot_id
order by cmnr.hub,cmnr.robot,cmnr.origin
Sreenathmp, I'm assuming you are installing the Nimsoft agent using the "Deploy Robots" option from USM. If this is the case, you could use the logmon probe and monitor the log file of the automated_deployment_engine probe on the respective hub that deploys the agent file.
In the log file "\\Nimsoft\probes\service\automated_deployment_engine\automated_deployment_engine.log", you could monitor for string such as "Package: 'robot_exe' finished".
You may need to change the log level on the automated_deployment_engine probe to level 3 if the default doesn't show enough information. Also, if you have multiple hubs that deploy the Nimsoft agent, you'll need to monitor each of these separately.
Hope this helps.