Configuring after installation
Configuring various capabilities of the KM
We can classify the Linux KM monitoring capabilities in four categories:
Local Monitoring
If you want to monitor your Linux hosts locally, you can configure the following monitor types in any combination as per your requirements.
- Default - Helps you configure disks, filesystems, processes, and Sudo execution mode
- Basic - Helps you configure filesystems and Sudo execution mode
- Processes - Helps you configure Processes
- Storage - Helps you configure disks and filesystems
Remote Monitoring
Select the Remote Monitoring monitor profile if you want to monitor your Linux hosts remotely.
The KM also enables you to remotely monitor your Linux hosts from a PATROL Agent running on Microsoft Windows operating system.
Linux Virtualization
Select the Linux Virtualization monitor profile if you want to configure OS monitoring for guests that are discovered below the Kernel-based virtual machine remotely.
With this profile, you can monitor the basic health of your guest virtual machines, include or exclude guest virtual machines from monitoring and configure Processes, FileSystems, and Disks for individual or a group of guests.
Red Hat Enterprise Virtualization
Select the Red Hat Enterprise Virtualization monitor profile if you want to monitor your RHEV environment. You can also configure filters for data centers, clusters, hosts, and virtual machines.
The following diagram is a pictorial representation of the monitor profiles and monitor types available in PATROL for Linux KM from the TrueSight and the Central Monitoring Administration console.
Each of these blocks contains a hyperlink that takes you to the respective monitor type configuration page. You can configure the monitor types as per your requirements (local, remote, Linux Virtualization, and RHEV).
Select the All to configure the available monitor types with their default settings.
Configuring in older consoles
This section provides instructions for configuring PATROL for Linux and RHEV components in the PATROL consoles. The PATROL for Linux and PATROL for RHEV KMs need no particular configuration before they begin collecting data after loading. However, there are a few configuration options that you might want to set up, depending on the needs of your environment.
Goal | Link |
|---|---|
Use the PATROL for Linux menu commands to configure the KM | |
Use the PATROL for RHEV menu commands to configure the KM | |
PATROL for Linux KM dialog boxes | |
PATROL for RHEV KM dialog boxes |