Using Foglight for Infrastructure
Host availability alerting
Virtual hosts and reported metrics
Exploring the Infrastructure Environment dashboard
Monitoring log files with Foglight Log Monitor
Accessing the Infrastructure dashboard
Selecting a service
Running a report for the Infrastructure Environment
Exploring the Monitoring tab
Exploring monitored hosts
Exploring the FAQ Question Viewer
Exploring the Administration tab
Using Foglight for Infrastructure agents
Using the PowerVM HMC agent
Using the UnixAgentPlus
Monitoring remote hosts
Deploying Foglight for Infrastructure agents
Creating agent instances
Defining credentials
Activating the agent
Monitoring the infrastructure
Adding a monitored host
Adding multiple monitored hosts
About the WindowsAgent
About the UnixAgentPlus
About the UnixAgent
About the MultiHostProcessMonitorAgent
Configuring monitoring agents
Investigating log records
Configuring agent properties
Monitoring IBM PowerVM environments
Configuring File Log Monitor agent properties
Configuring connections to remote Windows platforms
Monitored Hosts
Log Files
File Formats
Record Transformations
Data Collection Scheduler
FileLogMonitor configuration example
Configuring Windows Event Log Monitor agent properties
Before you begin
Managing PowerVM HMC agents
Advanced system configuration and troubleshooting
Reference
Configuring HMC user accounts
Configuring PowerVM HMC agent credentials
Creating PowerVM HMC agents
Reviewing and editing PowerVM HMC agent properties
Monitoring your PowerVM environment
Exploring the Infrastructure Environment dashboard
Investigating the collective use of all HMC resources
Viewing HMC details
Identifying top consumers of managed server resources
Viewing individual managed server details
Identifying top consumers of PowerVM partition resources
Viewing individual PowerVM partition details
Identifying top consumers of PowerVM virtual I/O server resources
Viewing individual PowerVM VIOS details
Investigating additional managed server, partition, and VIOS details
Exploring PowerVM partition and PowerVM VIOS overviews
Exploring managed server profiles
Investigating the use of PowerVM partition and VIOS processor resources
Investigating the use of PowerVM partition and VIOS memory resources
Exploring processor, memory, and storage breakdowns
Investigating volume-based storage pools
Exploring top resource analyzers
Exploring PowerVM VIOS network summaries
Drilling down on shared network adapters
Drilling down on physical and virtual network adapters
Investigating object dependencies
Reviewing frequently asked questions
Advanced System Configuration
Foglight for Infrastructure views
Foglight Log Monitor views
Rules
Metrics
Appendix: Building regular expressions in Foglight
AIX metrics
HP-UX metrics
Linux metrics
Solaris metrics
Windows metrics
AIXHostDetails topology object
AIXMemoryDetails topology object
AIXPhysicalCPUUsage topology object
AIXUsedMemoryDetails topology object
CPUCounts topology object
Host topology object
HostCPUs topology object
HostNetwork topology object
HostProcess topology object
HostProcessInstance topology object
HostService topology object
HostTopProcessEntry topology object
LPARNetworkInterfaceDetails topology object
LPARPhysicalDiskDetails topology object
LogicalDisk topology object
MSCluster topology object
MSClusterNode topology object
MSClusterResource topology object
MSClusterResourceGroup topology object
MSHostedResourceGroup topology object
Memory topology object
NetworkInterface topology object
NetworkInterfaceDetails topology object
NixHostProcessInstance topology object
OperatingSystem topology object
PhysicalDisk topology object
PowerVMVIOS topology object
PowerVMVIOSCPUs topology object
PowerVMVIOSMemory topology object
PowerVMVIOSNetwork topology object
PowerVMVIOSStorage topology object
Processor topology object
WinHostProcessInstance topology object
Supported platforms
For a list of platforms supported for the UnixAgent, see “System Requirements” in the Foglight for Infrastructure Release Notes.
Agent properties
When an agent connects to the Foglight Management Server, it is provided with a set of properties that it uses to configure its correct running state. For more information about working with agent properties, see Creating agent instances.
Figure 12. UnixAgent properties
You can configure the following settings for this agent:
|
• |
|
• |
Host: host name or IP address. |
|
• |
Host name override: host name to be used to store this host’s data in the Foglight data model. |
|
• |
Port: SSH port on which the agent connects. Default value = 22. |
|
• |
Top CPU Processes: number of top CPU processes to be monitored. Default value = 5. |
|
• |
Top Memory Processes: number of top memory processes to be monitored. Default value = 5. |
|
• |
Top IO Processes: number of top IO processes to be monitored. Default value = 5. |
|
• |
Use native collector (if available): Default value = True. |
|
IMPORTANT: Using the native collector to monitor an HP-UX system requires that the monitoring UnixAgent’s account belong to the sys and bin groups on the monitored system. Failing to add the account to these groups prevents the agent from collecting some logical disk metrics. |
|
• |
Aggregate data for all instances of a program: Default value = True. When set to True, the agent collects data from all the instances of a program (for example all Oracle® instances), aggregates the information, and presents it in a unified report. |
|
• |
Collect Top N Process Details: Default value = True. When set to True, the agent collects data for the Top CPU Processes, Top Memory Processes, and Top IO Processes. Details about these top processes are accessible from the Infrastructure Environment dashboard (for example, to see the top CPU processes, in the Monitoring tab, select a host on the Quick view, click the Explore button in the Resource Utilizations view, and click any metric indicator in the CPU area; the top CPU consumers are displayed in the CPU Details dashboard.) |
When set to False, some extra details (owning username/domain) are unavailable for processes reported in the various “Top N” collections. Gathering this information can be expensive if the connection to the remote machine is slow or the “Top N” collections are configured to be very large.
|
• |
Collect process metrics: Default value = True. When set to True, the agent collects process metrics. |
|
• |
Collect CPU metrics: Default value = True. When set to True, the agent collects performance metrics about the system’s CPUs. |
|
• |
Collect disk metrics: Default value = True. When set to True, the agent collects performance metrics about the system’s disks. |
|
• |
Include filesystems mounted from memory: Default value = False. This property indicates to the agent whether or not to collect information about RAM disks. This information is typically collected when monitoring Linux® and Solaris® platforms, and not collected for HPUX and AIX® platforms. |
|
• |
Include mounted remote filesystems: Default value = False. When set to True, the agent collects metrics about remotely mounted disks. |
|
• |
Collect memory metrics: Default value = True. When set to True, the agent collects performance metrics about the system’s memory. |
|
• |
Collect network metrics: Default value = True. When set to True, the agent collects performance metrics about the network. |
|
TIP: If you are collecting basic host metrics using Foglight for VMware, you may need to set the Collect CPU/disk/memory/network metrics options to False, to prevent Foglight for VMware and Foglight for Infrastructure from reporting different or conflicting values. For Foglight for VMware, consider setting all four flags to False. |
|
• |
Collect System ID: Default value = True. This property indicates to the agent whether or not to collect a unique system ID from this system. This is not always desirable when monitoring Hyper-V® systems, as some Hyper-V systems use the same ID for multiple systems and are not unique. |
|
• |
Collect Hypervisor metrics: Default value = False. This property indicates to the agent whether or not to collect additional metrics from hypervisor systems (for example, Solaris global Zone, AIX® LPAR, and so on). |
|
• |
Use ping to validate host availability: Default value = False. When set to True, the agent is configured to use ping to detect if the monitored host is unavailable. If the agent fails to make a connection to the monitored host, and this property is set to True, the agent sends a ping command to the host. If the host does not respond, the Host.monitored observation is set to UNAVAILABLE (for more details, see Host availability alerting). |
|
NOTE: When the Use ping to validate host availability property is enabled on a UNIX® platform, the sudoer file needs to configured to allow the ICMP process to run with NOPASSWD. For details, see Configuring secure launcher permissions using sudo. |
|
• |
Use commands with sudo: Default value = False. When set to False, the agent does not use commands that require sudo, and does not collect metrics that require root permissions. For more information about sudo commands that require root access, see Configuring secure launcher permissions using sudo. |
|
• |
Filter local disks based on declared filesystem types: Default value = True. When set to True, the agent enables the local filesystem type filtering. |
|
• |
Path to sudo command: The path to the sudo executable. |
|
• |
Process Availability Config: A list of monitored processes and their expected instance counts. The list contains three columns: Process Name, Command Line, and Expected Process Count, and can be edited, as required. The agent compares the number of actual processes with the number of expected processes, found in this list. Results are displayed in the Processes > User Defined Processes (Process Availability Config) view (for details, see User Defined Processes (Process Availability Config)). |
|
• |
Solaris: Execute the “/usr/bin/ps -e -o uid,pid,ppid,vsz,rss,time,pcpu,sid,s,user,comm,args” command. Then you will get the following process details. |
|
• |
Exclude/Include FileSystems: The type of FileSystems list to be used for monitoring. |
|
• |
Exclude (default) indicates that the file systems listed in the FileSystems list should be excluded from monitoring. |
|
• |
Include performs system monitoring on the file system that you are defining. |
|
• |
Filesystem Config: A list of file systems that are excluded from monitoring (if the Exclude/Include FileSystems property is set to Exclude) or included in the monitoring (if the Exclude/Include FileSystems property is set to Include). You can modify, clone, and delete lists of excluded/included file systems, as necessary. The list contains three columns: MountPoint regular expression, Remote host name regular expression, and Monitored host regular expression. An entry in the list consists of three regular expressions that together identify one or more file systems that are excluded from/ included in the monitoring. For example: |
|
If set, the file systems with the matching mount point should be excluded/included. In this example: All file systems located in /workspace. | ||
|
In this example: All remote hosts starting with “tor” such as tor.test.com or tor.prod.com. | ||
|
In this example: All hosts starting with “tor” such as tor.test.com or tor.prod.com. |
Click Edit to modify the entries in the list. In the HostAgents - UnixAgentPlus - ListName dialog box that appears, you have several options: add or delete rows, edit the existing entries, select file systems to be excluded/included, save or revert changes. To exclude/include one or more file systems from monitoring, add table rows entries and populate them with regular expressions, as required.
Click Clone to clone the selected exclude/include list. In the Clone ListName dialog box that appears, enter a name for the new list, and click OK to save the it. The new exclude/include list is added to the drop-down list.
Click Delete to delete the selected exclude/include list. In the Delete ListName dialog box that appears, confirm the deletion by clicking Yes. The exclude/include list is deleted from the drop-down list.
|
• |
Collector Config: defines how quickly the agent collects data. UNIX® provides a defaultSchedule configuration. Users can modify, clone, and delete configurations, as necessary. |
Click Edit to modify the configuration selected from the drop-down list. In the HostAgents - UnixAgent - ConfigurationName dialog box, you have several options: add or remove rows (that is, collectors and their settings), modify fields, and save or revert changes.
Click Clone to clone the configuration selected from the drop-down list. In the Clone ConfigurationName dialog box, enter a name for the new configuration, and click OK to save the it. The new configuration is added to the drop-down list.
Click Delete to delete the configuration selected from the drop-down list. In the Delete ConfigurationName dialog box, confirm the deletion by clicking Yes. The configuration is deleted from the drop-down list.
To this effect, the sudo configuration file (/etc/sudoers) must be configured so that password prompts are not required for a number of executables. The commands requiring elevated privileges differ by platform. The following commands must be configured for this version of Foglight for Infrastructure.
|
Some AIX versions require elevated permissions to access virtual memory information. | ||
|
Used to read IO statistics from the /proc filesystem. | ||
|
/sbin/ethtool or /usr/sbin/ethtool (depending on distribution) /sbin/mii-tool or /usr/sbin/mii-tool (depending on distribution) |
Used to determine the network card bandwidth; ethtool is favoured if it is found. | |
|
Oracle Solaris agents do not require sudo access. | ||
|
HP-UX agents do not require sudo access. |
The following is an example of how to configure the /etc/sudoers file to allow the user foglight to execute Linux® commands without being prompted for a password:
In addition, the requiretty flag must not be set in /etc/sudoers for the user, since Foglight for Infrastructure agents use non-interactive shells.
The following is an example of how to unset the requiretty flag for a single user named foglight, so that this user can run sudo commands remotely:
|
NOTE: If requiretty flag is set, sudo can run only when the user is logged in to a real tty. When this flag is set, sudo can only be run from a login session and not via other means, such as cron or cgi-bin scripts. This flag is off (unset) by default. |
Depending on the user’s sudo and syslog.conf configuration, sudo use may result in excess logging. To minimize the amount of log messages, ensure that sudo does not make use of the LOG_INPUT or LOG_OUTPUT tags for the commands that the UnixAgent runs. Depending on the existing monitored hosts’ configuration, any lines added to the /etc/sudoers file for Foglight monitoring may have to include NOLOG_OUTPUT or NOLOG_INPUT to override the default configuration. For example, for a user named foglight connecting to a monitored host, the following lines are required:
foglight ALL = NOLOG_INPUT: ALL, NOLOG_OUTPUT: ALL, NOPASSWD: /usr/bin/svmon
foglight ALL = NOLOG_INPUT: ALL, NOLOG_OUTPUT: ALL, NOPASSWD: /usr/bin/find|,
The last argument in this syntax depends on the type and location of the tool, ethtool or mii-tool, used to determine the network card bandwidth. If you are unsure which tool your system uses, you can specify all of them:
foglight ALL = NOLOG_INPUT: ALL, NOLOG_OUTPUT: ALL, NOPASSWD: /usr/bin/find|,
/bin/cat, /sbin/ethtool, /usr/sbin/ethtool, /sbin/mii-tool, /usr/sbin/mii-tool
For complete information about sudo and /etc/sudoers, refer to the sudo and /etc/sudoers man pages.
About the MultiHostProcessMonitorAgent
There are views, rules, and data associated with this agent. For more information, see Reference
For more details, see these topics:
Supported platforms
For a list of platforms supported for the MultiHostProcessMonitorAgent, see “System Requirements” in the Foglight for Infrastructure Release Notes.