HPE IMC APM Linux Application Monitor Configuration Examples

HPE IMC APM Linux Application Monitor Configuration Examples Part number: 5200-1355 Software version: IMC APM 7.2 (E0401) Document version: 1 The information in this document is subject to change without notice. Copyright 2016 Hewlett Packard Enterprise Development LP

Contents Introduction 1 Prerequisites 1 Configuration restrictions and guidelines 1 Example: Using APM to monitor Linux 2 Network requirements 2 Adding a Linux application monitor 2 Configuring global thresholds for the Linux application monitor 4 Verifying the configuration 5 Viewing the Linux application monitor report 5 Viewing a threshold alarm 12 i

Introduction This document provides examples for configuring APM to monitor Linux applications in a data center. Linux is a popular open source operating system. Its running affects services on the system. By monitoring Linux, you can understand the performance of the Linux application. Prerequisites Before you configure APM to monitor a Linux application, complete the following configurations: Start the Linux operating system. Make sure the APM server can communicate with the Linux application. To view traffic statistics in the monitor report of the Linux application, make sure at least one probe is configured in APM. Perform one of the following tasks: To monitor the Linux application through an agent, deploy the agent on the host on which the Linux operating system is installed. To monitor the Linux application through SNMP: Enable and configure SNMP for the host on which the Linux operating system is installed. For more information about enabling SNMP on Linux, see the Linux help. Obtain the read-only community strings. To monitor the Linux application through CLI: Enable and configure Telnet or SSH on Linux. For more information about enabling Telnet or SSH on Linux, see the Linux configuration guide. Obtain the user name and password of the Telnet or SSH user who has the Linux administrator's privileges. Configuration restrictions and guidelines When you configure APM to monitor the Linux application, follow these restrictions and guidelines: To monitor the following IPMI indexes, set Use IPMI to Enable when you add the Linux application monitor: Memory. Power supply. Temperature. Fan. Board. Chassis. If the Linux application is monitored through SNMP, you cannot monitor the following indexes: I/O state. Error log. Version. inode. Zombie process. 1

Zombie process number. Vol group. Session information. Example: Using APM to monitor Linux Network requirements As shown in Figure 1, a company has multiple Linux VMs running on a server in the data center. The server administrator intends to monitor the Linux operating systems by using APM. Figure 1 Network diagram Table 1 Host addresses and software versions Host IP address Software version Windows Server 2008 R2 IMC 172.4.95.21 IMC PLAT 7.2 (E0403) IMC APM 7.2 (E0401) Server 192.168.40.61 Red Hat Enterprise Linux 6.4 (Santiago) Adding a Linux application monitor 1. Log in to IMC. 2. Click the Resource tab. 3. From the navigation tree, select Application Manager > Add Application. 4. Click Linux of the Linux Server Monitor category. 5. Enter the IP address 192.168.40.61 of the host where the Linux application to be monitored is installed in the IP Address field. The Name field is automatically populated with Linux_192.168.40.61. 6. Set the monitor type: a. Select SSH from the Monitor Type list. b. Click the Configure icon. c. In the dialog box that appears, select Password from the Authentication Mode list. d. Enter the SSH user name and password in the Username and Password fields, respectively. e. Use the default settings of other parameters. f. Click OK. 7. Enable IPMI monitoring: a. Select Enable from the Use IPMI list. b. Enter the IP address of the baseboard management controller (BMC) for IPMI monitoring. 2

c. Enter the user name and password of the BMC for IPMI monitoring. 8. Use the default settings of other parameters. Figure 2 Adding a Linux application monitor 9. Click OK. The application monitor named Linux_192.168.40.61 appears on the application monitor list, as shown in Figure 3. Figure 3 Viewing the application monitor list 3

Configuring global thresholds for the Linux application monitor 1. Click the Resource tab. 2. From the navigation tree, select Application Manager > Configurations. 3. Click Threshold Configuration. The Threshold Configuration page appears. 4. Click the Global Threshold tab. 5. Click Linux Server Monitor next to Application Category. 6. Click Linux next to Application Type. The list displays all Linux indexes for which you can configure thresholds, as shown in Figure 4. Figure 4 Global threshold list This example describes threshold settings of the File System Usage Ratio parameter. 7. Click the Modify icon for the File System Usage Ratio parameter. The Modify Threshold page appears. 8. Configure the following parameters, as shown in Figure 5: Select Enable from the Enable Level-1 Threshold list. Set a level-1 threshold value in the Threshold field. Set an alarm trigger frequency in the Trigger Times field. Select Enable from the Enable Level-2 Threshold list. Set a level-2 threshold value in the Threshold field. Set an alarm trigger frequency in the Trigger Times field. APM generates a level-1 or level-2 threshold alarm when the File System Usage Ratio parameter meets the alarm trigger conditions for the level-1 or level-2 threshold. 4

Figure 5 Modifying thresholds 9. Click OK. Verifying the configuration Viewing the Linux application monitor report 1. Click the Resource tab. 2. From the navigation tree, select Application Management > Application Monitor. The application monitor list displays all application monitors. 3. Click Linux_192.168.40.61 to display the report. Figure 6 shows part of the Linux application monitor report. The report contains index values obtained from the most recent polling of the application. Figure 6 Linux application monitor report 5

The following sections describe some fields in the report. CPU Usage Ratio The CPU Usage Ratio area contains the following fields, as shown in Figure 7: CPU Usage Ratio CPU usage ratio of the Linux application. Click the Set Threshold icon to set alarm thresholds for the CPU usage. History Record Click the History Record icon to view the history graph of the CPU usage ratio. Figure 7 CPU Usage Ratio Memory Usage Ratio The Memory Usage Ratio area displays information about physical memory and swap memory. The Memory Usage Ratio area contains the following fields, as shown in Figure 8: Physical Memory Physical memory of the Linux application, which corresponds to the physical memory bar. Swap Swap memory of the Linux application, which corresponds to a disk space. Total Total amount of the physical or swap memory. In Use Size of the physical or swap memory in use. Click the History Record icon to view the history graph of the physical or swap memory in use. Usage Ratio Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/total memory x 100%. Click the Set Threshold icon to set alarm thresholds for the physical or swap memory. Click the History Record icon to view the history graph of the physical or swap memory usage. 6

Figure 8 Memory Usage Ratio Ping Test When the polling interval expires, APM pings the Linux host by sending a maximum of three ICMP packets. When APM receives a response, it considers the ping test a success and records the response time. When APM receives no response after sending out all ICMP packets, it considers the ping test a failure. The Ping Test area contains the following fields, as shown in Figure 9: Response Time Round trip response time of the Linux application. Click the History Record icon to view the history graph of the response time. Packets Sent Number of ICMP packets that are sent. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets. Packets Received Number of ICMP response packets that are received. The value is 0 or 1. Click the History Record icon Figure 9 Ping Test to view the history graph of the received packets. System Load APM counts the average system load over 1 minute, 5 minutes, and 15 minutes. The average system load records the average number of processes in the run queue over a specific time interval. An overloaded system results in severe performance issues. The load threshold value varies by CPU model. The System Load area contains the following fields, as shown in Figure 10: System Load/Min Average system load over the last 1 minute. Click the History Record icon to view the history graph of the system load over the last 1 minute. 7

System Loads/5 Min Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the system load over the last 5 minutes. System Loads/15 Min Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the system load over the last 15 minutes. Figure 10 System Load File System Usage Ratio The Linux file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system corresponds to a physical disk partition or logical volume. Use the File System Usage Ratio area to display how the available disk space is used. The File System Usage Ratio area contains the following fields, as shown in Figure 11: Name Mount point of the file system in the Linux directory structure. File System Usage Ratio Space usage ratio of the Linux file system. Click the Set Threshold icon to set alarm thresholds for the file system usage. Click the History Record icon to view the history graph of the file system usage ratio. In Use Used space of the file system. Click the History Record icon to view the history graph of the used file system space. Free Space Free space of the file system. Click the History Record icon to view the history graph of the free file system space. Figure 11 File System Usage Ratio 8

Network Interface The Network Interface area contains the following fields, as shown in Figure 12: Interface Name Identifier of a network interface card in Linux. APM monitors both physical and virtual (logical) network interface cards. Receive Rate Receive rate of a network interface card. Click the Set Threshold icon to set alarm thresholds for the receive rate of Linux network interface cards. Send Rate Send rate of a network interface card. Input Error Packet Rate Number of inbound error packets per second on a network interface card. Output Error Packet Rate Number of outbound error packets per second on a network interface card. Figure 12 Network Interface Process By default, the list does not contain any processes. To monitor processes on Linux, click the Configuration icon to select the processes to be monitored. APM collects the index data for the monitored processes when APM polls applications next time, including the CPU usage ratio and memory usage ratio. The Process area contains the following fields, as shown in Figure 13: Config Click the Config icon to select processes to be monitored in the monitor list window. Process Name Name of the monitored process. For processes with the same name but different Process Identifiers (PIDs), APM collects the CPU usage ratio and the memory usage ratio for each process. For example, the Apache application might generate a lot of httpd processes, and APM collects the CPU usage ratio and the memory usage ratio for each httpd process selected. ID Unique identifier of the process on the operating system. Parent ID ID of the parent process for the process. CPU Usage CPU usage ratio of the process. Click the Set Threshold icon to set alarm thresholds for CPU usage. Click the History Record icon to view the history graph of CPU usage. Memory Usage Memory usage ratio of the process. Click the History Record icon to view the history graph of memory usage. CPU Time Duration that the process occupies the CPU. 9

Figure 13 Process I/O State APM can monitor the I/O status of disks, partitions, or logical volumes in Linux. The I/O State area contains the following fields, as shown in Figure 14: Device Name Name of the disk, partition, or logical volume in Linux. I/O Read Rate Data output rate of the disk, partition, or logical volume in Linux. I/O Write Rate Data input rate of the disk, partition, or logical volume in Linux. Figure 14 I/O State inode The inodes are required when you create a file or directory in the Linux file system. If inodes are used up, you cannot create a file or directory in the file system. The inode area contains the following fields, as shown in Figure 15: File System File system on the Linux server. Total Total number of available inodes in the file system. Click the History Record icon to view the change trend of the total number of inodes in the file system. Free Number of inodes that are not used in the file system. Click the History Record icon to view the change trend of the number of idle inodes in the file system. In Use Number of inodes that have been used in the file system. Click the History Record icon to view the change trend of the number of used inodes in the file system. inode Usage Ratio Usage of inodes in the file system. Click the Set Threshold icon to set alarm thresholds for file system inode usage. Click the History Record icon to view the history graph of inode usage in the file system. 10

Figure 15 inode Vol Group Logical volume management manages disk partitions in the Linux operating system. It combines one or more physical disks to a volume group and creates a logical volume for the volume group. One logical volume equals a disk partition. The Vol Group area contains the following fields, as shown in Figure 16: Name Name of the volume group. Size Size of the volume group. Click the History Record icon to view the history graph of volume group size. In Use Volume group space in use. Click the History Record icon to view the change trend of used volume group space. Free Space Volume group space that is not used. Click the History Record icon to view the history graph of free volume group space. Usage Ratio Usage of volume group space. Click the Set Threshold icon to set alarm thresholds for space usage of the volume group. Click the History Record icon to view the history graph of space usage of the volume group. Figure 16 Vol Group Session Information The Session Information area displays Linux session login information. The Session Information area contains the following fields, as shown in Figure 17: User Name User who has logged in to Linux. TTY TTY used by the user. Login IP Client IP address used by the user to log in to Linux. The value of :0 indicates that the user logs in to Linux through the console. Login Time Time when the user logged in to Linux. Idle Idle time after the user logged in to Linux. Command Most recently executed command after the user logged in to Linux. 11

Figure 17 Session Information Viewing a threshold alarm 1. Open the Linux application monitor report. When a threshold alarm is generated, the health status of the Linux application monitor changes. The Monitor Information area displays the unrecovered alarms, as shown in Figure 18. Figure 18 Monitor information 2. Click the alarm information to view alarm details, as shown in Figure 19. 12

Figure 19 Alarm details 13