how do we tell the account a robot or probe is running under?

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We need to know if a robot or probe is running under a user. How can we tell?

Environment

23.4 and above

Resolution

This is a complex question to answer as it depends on the OS and what the robot is doing.

If the Windows database for the UIM is using a domain account, then the robot service for the primary UIM and any robot running wasp needs to have the service set to the same domain account. See Requirements for Windows Authentication
You can also now run robots as non-admin or root accounts, see  Install DX UIM as a Non-Admin/Non-Root User for more information.

To determine which account a Broadcom UIM (Unified Infrastructure Management) robot is using, you need to check the OS-level user running the controller process. By default, robots run as root on Unix/Linux and LocalSystem on Windows, but they can be configured to run as specific user accounts. 

Here are the methods to verify the user account:

 

1. Check Locally on the Machine (Most Reliable)

• Windows: Open the Services snap-in (services.msc), find the Nimsoft Robot Watcher service, and check the "Log On As" column.
• Linux/Unix: Log in to the machine and run the following command to check the process owner:
  bash ps -ef | grep controller
  The first column in the output indicates the user (e.g., root, nimuser). 

2. Broadcom DX UIM (Unified Infrastructure Management) probes often require specific account credentials to authenticate against target systems and gather data, particularly for remote monitoring and application management. Key probes using accounts include rsp (Remote System Probe) for SSH/WMI credentials, webgtw for CA UIM server authentication, and various application/database monitors like db2, oracle, and sql_server.

System/Remote Monitoring: The rsp (Remote System Probe) requires credentials (username/password or key) for SSH on Linux/UNIX or WMI on Windows to collect data on CPU, disk, memory, and load.

• Database & Application Probes: Probes like sql_server, db2, oracle, mysql, and postgresql require database-specific user credentials to connect, query performance metrics, and manage monitors.
• Infrastructure & Storage: Specialized monitoring probes such as netapp_ontap, ceph_storage, vmax, vnxe_monitor, and vplex (EMC) use service accounts to access storage APIs.
• Web & Application Servers: Probes like tomcat and weblogic use credentials to access JMX interfaces for monitoring Java applications.