ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Some questions regarding the audit probe


Article ID: 33949


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) NIMSOFT PROBES


Q1. We have not enabled "audit" on any robot.
However, in audit probe GUI I see some audit records such as

"Login: succeeded for administrator"
"Login: succeeded for discovery_server"
"Login: succeeded for discovery_agent"
"Login: succeeded for baseline_engine"
"Login: succeeded for dashboard_engine"
"Login: succeeded for dist_srv"

"probe" column for these records - shows "hub".

As far as we understand correctly, we are supposed to see audit records only for a robot where "audit" is enabled. Can you please explain why we are seeing such audit records ?

Q2. We may opt to disable "audit" probe.
We want confirmation if there is any expected negative impacts to NMS when "audit" is disabled.

NMS 7.5


A1. These records are published by hub probe, rather than by controller (robot) probe.
Therefore, as far as "audit" Subject is subscribed, it is relayed into NMS's audit probe.

You can configure the hub probe NOT to publish such records by a configuration key in the hub.cfg <hub> section:


A2. The only functional loss is to the audit probe "callback of controller probe"

NMS core monitoring capability (QoS collection, alarm collection) remains unaffected.



Component: UIMAUD