Page History

...

Although agentless monitoring is supported, you can also use up.time Agents to retrieve detailed performance metrics (such as CPU, memory, process, disk, and network usage) from systems that you are monitoring. up.time Agents can also securely and remotely execute programs; for example, the Windows Agent can start and stop services, and reboot the system. You will install Install an up.time Agent on each monitored system whose metrics are not being collected by some agentless method. Agents support a variety of operating systems.

...

• The installation procedure creates an uptime user ID on the Monitoring Station. This uptime user should also exist on all systems that will have an up.time Agent; using this ID on monitored systems will minimize minimizes any security risks by not running the Agents as a privileged process.
• Wherever possible, do not use the root account to run the Monitoring Station or up.time Agents.
• You can use existing user accounts for the agent, such as nobody, bin, or adm; however, using these accounts may pose security risks depending on other system processes that run under these accounts.
• On HP/UX, you cannot start processes, such as up.time Agents, using the nobody user ID.
• On Windows operating systems, the up.time Agent must be running with Administrator privileges. If it is not, the up.time Agent will not be able to cannot access the system performance counters.

...

• identified the system that will act acts as the central Monitoring Station
• identified which servers, instances, and network devices will be are monitored
• ensured systems that will host the up.time Agent are on the supported platforms list for this release
• ensured all systems that you want to monitor are accessible over the network
• have downloaded the appropriate install file from the up.time Support Portal
  
  • up.time-<version>-linux.bin
  • up.time-<version>-windows.exe

...