IBM. IBM Cloud Automated Modular Managed (AMM) - monitoring services User Guide

Transcription

1 IBM Cloud Automated Modular Managed (AMM) - monitoring services User Guide Version IBM Cloud Automated Modular Managed (AMM) - monitoring services User Guide IBM

2

3 IBM Cloud Automated Modular Managed (AMM) - monitoring services User Guide Version IBM Cloud Automated Modular Managed (AMM) - monitoring services User Guide IBM

4 Note Before using this information and the product it supports, read the information in Notices on page 53.

5 Contents Preface v Audience v Chapter 1. Service Page Chapter 2. Working with IBM Cloud AMM - monitoring service Prerequisites Open Service Page Reset Admin User Password Contact the Support Team Chapter 3. Deploying Monitoring Agents 5 Manage and Delete Agents from the Administrative UI Manage Agents from Administrative UI Remove Agents from Administrative UI Install Agents Manually on SoftLayer Devices... 6 Install Agent Manually on Linux Install Agent Manually on Windows Install Agents Manually on VMware Guest VMs (private IP) Manual Agent Installation on VMware Linux Guest Devices Manual Agent Installation on Devices with Only Private IP Chapter 4. Setting Up VMware Hosts for Monitoring Add VMware Host Manually Run Discovery Manually Chapter 5. Working with the Zabbix UI 13 Open Zabbix UI Verify Host Status Applying Templates Apply OS Template Manually Apply MySQL Monitoring Template to Devices 16 Apply Microsoft SQL Server Template to Devices 17 Apply Apache Monitoring Template to Device.. 19 Apply VMware Template Operating System and Base Resource Monitoring from Zabbix UI CPU Utilization Memory Usage Disk Space Usage Configuration Alert Configuration Create Action Enable/Disable alerts Database Monitoring Viewing MySQL Monitoring Data on Dashboard 28 Triggers Based on MySQL Service Status Configuring alerts Apache Web Server Monitoring Viewing Apache monitoring data on dashboard 29 Triggers Based on Apache Service Status VMware Monitoring Viewing Hypervisor Data on Dashboard SNMP Monitoring SNMP Monitoring for RHEL Device SNMP Monitoring for Windows 2012 Device.. 33 SNMP Only Monitoring Administering the Monitoring Agent Restart Zabbix Agent Start and Stop Zabbix agent in Linux OS Start Zabbix agent in Windows OS Appendix A. Best Practices for Monitoring Large Environments Appendix B. Troubleshooting Cancel Installation Service Remove SoftLayer Devices from your IBM Cloud AMM - monitoring service Environment Admin UI Login or Empty Managed / Unmanaged List Sudo Level Commands on Zabbix Service Instance 42 Appendix C. Diagnosing Problems from the Agent Appendix D. Alert Forwarding Using ServiceNow Beta Architecture Deploying and Configuring ServiceNow Adapter.. 46 Deploying the Adapter adapter-config.cfg Deploy Configuring in Zabbix Caller script (call-alert.sh) Appendix E. Alert Forwarding Using IBM Tivoli Netcool Beta Notices Trademarks and Service Marks Copyright IBM Corp iii

6 iv IBM Cloud Automated Modular Managed (AMM): monitoring services

7 Preface This publication documents how to work with IBM Cloud AMM - monitoring service. Audience This information is intended for the users of IBM Cloud AMM - monitoring service. Copyright IBM Corp v

8 vi IBM Cloud Automated Modular Managed (AMM): monitoring services

9 Chapter 1. Service Page The Service Page is the landing page for IBM Cloud AMM - monitoring service. It has the details of the provisioned service, and includes all links that are required for the service. v IBM Cloud Marketplace - Marketplace to access the application. v Administrative UI Landing page of the service. It is the UI to manage agents. It has links to Zabbix UI and APIs. v Zabbix - UI of the Zabbix monitoring tool. It is used to configure monitoring environment of the Virtual Machine (VM). In addition, you can also manage and monitor the devices. v API - Swagger UI to execute custom APIs provided by the service. Copyright IBM Corp

10 2 IBM Cloud Automated Modular Managed (AMM): monitoring services

11 Chapter 2. Working with IBM Cloud AMM - monitoring service Prerequisites Open Service Page Prerequisite and steps to open IBM Cloud AMM - monitoring service. You must on-board devices manually or from IBM Cloud AMM - installation service (IS). To obtain a SoftLayer Account ID and on-board devices, see If you want a UI based agent installation, subscribe to the free IS before you subscribe to IBM Cloud AMM - monitoring service. Though the IS automatically discovers, you must on-board the devices by using IS UI. If you prefer not to use IS, then only standalone agent installation is supported. Attention: Before you start working with the service, clear your browser cache. Important: If you decide to install IBM Cloud AMM - monitoring service without the IS, then you cannot introduce IS at a later date. Also, the order of subscription and installation must be IS first followed by IBM Cloud AMM - monitoring service. You can open a IBM Cloud AMM - monitoring service instance from IBM Cloud Marketplace. Procedure 1. Go to IBM Cloud marketplace > My Services page, and click "IBM Cloud AMM - monitoring service". In case of managed service, request IBM Sales or AMM provider for the URL of the Service. The Service Page is displayed. After provisioning is complete, the status changes to green. The Admin password for the service is ed to the registered ID. Important: Only one administrator user is set up from IBM Cloud marketplace. After the admin user is established, access to the IBM Cloud AMM - monitoring service can be provisioned and multiple users of the service can be authorized within Zabbix UI. In addition, new users can be created and managed from the Zabbix UI. For more information on the steps to create and Copyright IBM Corp

12 Reset Admin User Password manage users, see Zabbix User guide - documentation/2.4/. There can be only one instance of IBM Cloud AMM - monitoring service per customer. 2. Click here link of the Administrative UI to manage agents and to work with Zabbix UI and swagger API interface. This administrator user (Admin) user is referred to as the master administrative user. About this task If Admin password is compromised, reset it for security purpose. Note: Do not change the Admin password from within the Zabbix UI. Procedure 1. In the service page, click Administrative UI link. 2. Enter the Admin password (master administrative user) that is ed to the subscribed ID. 3. Click Login. Contact the Support Team 4. Go to admin menu drop down list and select Reset Password. 5. In the Reset Password page, click Reset. The new password is ed to the specified address. Note: If you do not receive the due to any reason or you lose the , open a support ticket and the support team will reset the password. You will receive the password on the registered address. There are two methods to contact the support team from the IBM Cloud AMM - monitoring service UI. About this task The two methods to contact the support team are as follows: v Support menu in the Service page. v Support > Contact Us menu in the Administrative UI. Procedure 1. Open the Administrative UI from the Service page. 2. Click Support > Contact Us. 3. In the Contact Support page, enter the appropriate information and click Submit. You can also attach supporting files to provide additional inputs to the support team. 4 IBM Cloud Automated Modular Managed (AMM): monitoring services

13 Chapter 3. Deploying Monitoring Agents You can install the IBM Cloud AMM - monitoring service agents either manually or from the Administrative UI page. Manual agent installation requires more effort but is useful when you apply agents on a smaller number of devices that are from different SoftLayer accounts. Manual agent installation is also required whenever you do not use IBM Cloud AMM - installation service in your environment. The default communication between the Monitoring server and the agent is not encrypted, as Zabbix 2.4 does not support encrypted communication between the components. When you install agents, the service automatically installs Stunnel on both server and client to enable a secure communication between the server and the agents. For more information about Stunnel, see Only the master administrative user is authorized to deploy agents from the IS. To access the service, enter the Admin password (master administrative user) that is ed to the subscribed address. Important: v You are charged for every enabled VM in Zabbix (except for Zabbix server entry) irrespective of whether it is active or not. In the Zabbix UI, go to Configuration > Hosts to delete the unwanted VMs or hosts that you no longer manage. v Do not consult the Zabbix status icon to check for the host status. Instead, see the monitoring data of a host for its actual status (enabled or not). Manage and Delete Agents from the Administrative UI You can manage and delete agents automatically from the administrative UI of the service. Manage Agents from Administrative UI You can manage agents from the Administrative UI if you use the IS to on-board devices. Before you begin Before you deploy the agents to a SoftLayer virtual server, on-board them through IS. For the steps, see On-board VMs section. Procedure 1. In the service page, click Administrative UI link. 2. In the Login page, enter the Admin password (master administrative user) that is ed to the subscribed ID. 3. Click Login. 4. Go to AGENT MANAGEMENT > UNMANAGED. 5. In the UNMANAGED page, select one or more Device Names and click Manage. A confirmation message is displayed on the screen. Copyright IBM Corp

14 Remember: If changes do not reflect on your page immediately, refresh your browser. Note: If you click Manage without selecting any devices, then an error message is displayed. 6. You can track the progress in the AGENT MANAGEMENT > DEPLOYMENT HISTORY page. Note: If you click MANAGE for a device in the UNMANAGE page and it fails in the background, then in the DEPLOYMENT HISTORY page, Failed is displayed in the Status column. If the operation is in progress, then In progress is displayed in the Status column. Remove Agents from Administrative UI You can remove agents that are being managed by the IBM Cloud AMM - monitoring service. Procedure 1. In the Service page, click Administrative UI link. 2. In the Login page, enter the Admin password (master administrative user) that is ed to the subscribed ID. 3. Click Login. 4. Go to AGENT MANAGEMENT > MANAGED. 5. Select one or more devices and click UNMANAGE. A confirmation message is displayed on the screen. Note: If you click Unmanage without selecting any devices, then an error message is displayed. Remember: If changes do not reflect on your page immediately, refresh your browser. 6. You can track the progress in the AGENT MANAGEMENT > DEPLOYMENT HISTORY page. Install Agents Manually on SoftLayer Devices You can install and remove agents manually on Linux and Windows platform. Both manual and UI based agent install mechanism makes use of Zabbix APIs to register a device with Zabbix. Ensure that you are able to access the Zabbix server from the device that you are using to install the agent. You can use browser or curl command to make sure that you are able to login to the Zabbix UI. The Zabbix UI url is You can get the IP/DNS name of the AMM-MS-Public-InterfaceMonitoring-Service- Public-Interface from the Service page. For Windows and Linux platforms, both install and uninstall scripts require the same parameters and the syntax is as follows: v Install parameters: <Monitoring-Service-Public-Interface> <Monitoring-Service-Port> <Admin-Password> <SSL-Mode> <Deployment-Mode> v Uninstall parameters: <Monitoring-Service-Public-Interface> <Monitoring-Service-Port> <Admin-Password> 6 IBM Cloud Automated Modular Managed (AMM): monitoring services

15 Where, v Monitoring-Service-Public-Interface: The public interface of the IBM Cloud AMM - monitoring service. You can get the IP address from the status page of the service. v Monitoring-Service-Port: Use 443. v Admin-Password: Password of the Admin user that you received in your subscribed ID. v SSL-Mode: Communication method from agent to server. If you use SSL, then specify value as 'ssl'. If you do not want to use SSL communication for some reason, specify value as 'non-ssl'. v Deployment-Mode: This string appears in the Description field of the registered host. It specifies how the agent is deployed. Default value will be 'Standalone Deployment'. Important: Before you install a device, verify if there exists an entry for that device in Zabbix. The entry can be due to previous agent installation. Agent installation will fail if the host is already defined in Zabbix, so remove the entry before you install the agent. Install Agent Manually on Linux Prerequisites and the steps to install agent manually on Linux. Before you begin Ensure that the following prerequisites are met before you install agents manually on Linux OS: v The YUM repositories are configured correctly so that agent install process can pull Stunnel and other dependency packages. v As a user you have all the required permissions to install packages and access log directories. Procedure 1. Login (PuTTY or any other SSH / SFTP connection software) to the endpoint that is monitored by using the IP address and password that is available in your SoftLayer account. 2. Download amm-monitoring-agent.zip file from customer_access:qpm7h4xmemd6kpc9qfa@prdartifactory.mms.ibmcloud.com/artifactory/simple/customer-content/ monitoring/zabbix-agent/amm-monitoring-agent-lin-2.4.zip and copy it to a temporary location on the Linux device, for example, /tmp. Important: Always download the latest agent binaries from the AMM download location before you install the agent. The binaries are updated with latest features and defect fixes at regular interval of time. 3. Run the wget command to download Zabbix 2.4 agent - wget Qpm7H4XmEmD6Kpc9qFA@prd-artifactory.mms.ibmcloud.com/artifactory/simple/ customer-content/monitoring/zabbix-agent/amm-monitoring-agent-lin-2.4.zip 4. Decompress it to a location of your choice and open the directory. For example, if you extracted the files under /tmp/amm-monitoring-agent, then open that directory. Chapter 3. Deploying Monitoring Agents 7

16 unzip amm-monitoring-agent-lin-2.4.zip cd /tmp/amm-monitoring-agent-lin-2.4 Note: v Sometimes, extraction throws this error - [root@snmptestrhel tmp]# unzip amm-monitoring-agent-lin-2.4.zip -bash: unzip: command not found error exception. If you encounter this error, then run the following commands to install the zip: yum install unzip v Run this command in the location where you extracted the files to avoid permission denied error message - chmod 755 *.sh. 5. Run the script install-agent.sh. Syntax of the script is as follows:./install-agent.sh <Monitoring-Service-Public-Interface> <Monitoring-Service-Port><Admin-Password> <SSL-Mode> <Deployment-Mode> Note: Use the port To verify, go to Zabbix environment. An entry is created for the host in Zabbix and is monitored. 7. Apply required templates to the newly created host. For sample steps to apply templates, see Apply MySQL Monitoring Template to Devices on page To uninstall the agent, run uninstall-agent.ps1 -./uninstall-agent.sh <Monitoring-Service-Public-Interface> <Monitoring-Service-Port> <Admin-Password> Install Agent Manually on Windows Prerequisites and steps to install agent manually on Windows. Before you begin Run this command in PowerShell to set the script execution policy to un-restricted - Set-ExecutionPolicy Unrestricted. Ensure that you have all the required permissions to install packages, access log directories, create Windows services. Procedure 1. Download the AMM Zabbix agent package from AMM artifactory monitoring/zabbix-agent/amm-monitoring-agent-win-2.4.zip on Windows endpoint. For example, C:\ZabAgent. Important: Always download the latest agent binaries from the AMM download location before you install the agent. The binaries are updated with latest features and defect fixes at regular interval of time. 2. Extract the compressed file. 3. Open PowerShell and change to the directory where files are extracted. 8 IBM Cloud Automated Modular Managed (AMM): monitoring services

17 4. To set the execution policy to unrestricted, run Set-ExecutionPolicy Unrestricted. 5. Run the script install-agent.ps1. The syntax of the script is.\install-agent.ps1 <Monitoring-Service-Public-Interface> <Monitoring-Service-Port> <Admin-Password> <SSL-Mode> <Deployment-Mode>. 6. To verify, go to Zabbix environment. An entry is created for the host in Zabbix and is monitored. 7. To uninstall the agent, run uninstall-agent.ps1 script -.\uninstall-agent.ps1 <Monitoring-Service-Public-Interface> <Monitoring-Service-Port> <Admin-Password> Install Agents Manually on VMware Guest VMs (private IP) You can install the Service Agent manually on VMware guest devices that run on Linux and Windows operating system. However, there are few differences as compared to the agent installation and management for regular SoftLayer devices. Manual Agent Installation on VMware Linux Guest Devices If VMware Linux guest devices have an old OpenSSL package installed, then these devices fail to connect to the Monitoring Server due to the unsupported SSL level (SSLv3 mostly). IBM Cloud AMM - monitoring service only allows TLSv1 connections through Stunnel. In such a case, you will see the following errors in Stunnel log file (/etc/stunnel/stunnel.log), and the agent will report it as sent 0 bytes to the server :01:16 LOG3[26874: ]: SSL_connect: : error: :ssl routines:ssl3_read_bytes:sslv3 alert handshake failure :01:16 LOG5[26874: ]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket To get the agent working on such devices, ensure that you have the latest version of OpenSSL for a given OS version that supports TLS protocol. Otherwise, install the agent using non-ssl communication mechanism. Note: Non-SSL based communication mechanism is used only when the SSL based communication mechanism cannot be established due to technical limitations. Non-SSL based communication exposes the risk of allowing unauthorized access to the user data on an unsecure channel. To install the agent in non-ssl mode, provide the value non-ssl to the SSL-mode parameter of the install script../install-agent.sh <Monitoring-Service-Public-Interface> <Monitoring-Service-Port> <Admin-Password> non-ssl <Deployment-Mode> Chapter 3. Deploying Monitoring Agents 9

18 Manual Agent Installation on Devices with Only Private IP VMware guest devices are mostly with private only IP. They are not accessible from outside on any public interface. IBM Cloud AMM - monitoring service supports manual agent installation on devices that do not have public interface. Note: Devices must be able to access the IBM Cloud AMM - monitoring service from a public interface. The agent installation process is same as that of the SoftLayer devices. However, in case of VMware devices, the icon in the Availability column of the Zabbix UI always remain red. Even if you see agent interface icon as red, the agent sends data to the server and you can verify it in the Monitoring > Latest data section of the Zabbix UI. 10 IBM Cloud Automated Modular Managed (AMM): monitoring services

19 Chapter 4. Setting Up VMware Hosts for Monitoring The IBM Cloud AMM - monitoring service supports the monitoring of VMware hosts. This allows basic monitoring of VMware hosts without applying agents. This section provides the steps to manually add and discover VMware hosts. Prerequisites for working with VMware are as follows: v A bare metal ESX server with VMware OS from SoftLayer v Devices on top of ESX Add VMware Host Manually Procedure 1. In the Service UI, navigate to Configuration > Hosts. For the steps to open the Service UI, see Open Zabbix UI. 2. Click Create Host. 3. Enter the following details on Host tab: v Host name Enter the FQDN (Fully Qualified Domain Name) of the ESX server as available on the Softlayer. For example, it is "devmonvmw1.amm.ibmcloud.com". v Visible name Enter the same value as host name. v Groups Add host to the required group. In this case, Hypervisors (as it is a bare-metal hypervisor). v Agent interfaces (IP address) Enter IP address of the endpoint to be monitored. In this case, IP of ESX server. 4. Click to open the Template tab. 5. Add Template Virt VMware template to the host. For steps to add templates, see section Applying Templates on page Click to open the Macros tab and enter the following details: v {$URL} - VMware service (vcenter or ESX hypervisor) SDK URL ( v {$USERNAME} - VMware ESX service user name v {$PASSWORD} - VMware ESX service {$USERNAME} user password 7. Click Save. Run Discovery Manually You can run discovery for VMware hosts and update host prototypes. Procedure 1. Make sure that your discovery results for Template Virt VMware template are similar to the example displayed. Copyright IBM Corp

20 2. Update the Host prototypes. Note: Discovered hosts are prefixed with the name of the discovery rule that created them, and they are displayed in the host list. You can manually delete the discovered hosts. However, the discovered hosts can also be automatically deleted depending on the Keep lost resources period (in days) value of the discovery rule. 12 IBM Cloud Automated Modular Managed (AMM): monitoring services

21 Chapter 5. Working with the Zabbix UI Open Zabbix UI This section describes the various components of IBM Cloud AMM - monitoring service. Service UI is used to perform the core activities of the Service. Prerequisites and steps to open a Zabbix UI. Before you begin Before using the service UI, ensure that the agents are installed either through the agent installation page or manually. Procedure 1. In the Service Page, click here link of Administrative UI. 2. Enter the Admin password (master administrative user) that is ed to the subscribed ID. 3. Click Login. 4. Click ZABBIX menu. 5. In the Zabbix log in page, enter admin for Username and enter the Password that is ed to the subscribed address. Note: Do not change the Admin user password (master administrative user) in Zabbix UI. AMM service uses this user to communicate with Zabbix and hence a change breaks the communication. 6. Click Sign in. Copyright IBM Corp

22 Verify Host Status Applying Templates Note: The AMM template OS Linux or Windows template is automatically installed. If it is removed or missing for any reason, reapply it manually. See section Apply OS Template Manually on page 15. Important: Bookmark the user interface for quick access. If you bookmark, then you do not have to go to IBM cloud marketplace > My Services page every time. Go to Monitoring > Latest Data to see the status of host monitoring. The Configuration > Host section has all the host entries with agent interface icon in gray color. Even if it is red initially, the scheduled task changes to gray. To support private network monitoring, IBM Cloud AMM - monitoring service uses all the ACTIVE checks that are defined in AMM supported templates. The agent sends data to the server to populate values for all such checks and Zabbix Server never connects with the agent. If you specify the real IP (public or private) of a device in the agent interface definition of Zabbix, then the agent interface icon turns to green for public devices and red for private devices. To avoid this inconsistent behavior, IBM Cloud AMM - monitoring service registers all the devices (whether it is public or private) with agent interface IP as This way all the host entries under Configuration > Hosts has a gray color for agent interface icon. Zabbix server might still connect to the endpoint on this dummy IP and mark the agent interface icon in RED. However, there is a scheduled task in IBM Cloud AMM - monitoring service that runs every 30 minutes and clears the agent interface icon status by making it to gray. IBM has created 8 separate customized templates, and they are "AMM template OS Linux", "AMM template OS Windows", "AMM template App MySQL", "AMM template App Apache", "AMM Template SNMP Agent OS Linux", "AMM Template SNMP Agent OS Windows", "AMM Template SNMP Only OS Linux", and "AMM Template SNMP Only OS Windows". 14 IBM Cloud Automated Modular Managed (AMM): monitoring services

23 For Zabbix related templates, see the following documentation, which are available in the community website: v v Apply OS Template Manually The IBM Cloud AMM - monitoring service provides custom templates for Linux and Windows operating systems - AMM Template OS Linux and AMM Template OS Windows. Both AMM Template OS Linux and AMM Template OS Windows templates are automatically installed based on the operating system of your device. If it is removed or missing for any reason, you must manually reapply it. Procedure 1. Navigate to Configuration > Hosts. 2. Click a host name link to monitor the database. 3. Switch to Templates tab. 4. Click Select link to add a new template to the host. Note: There are many out-of-the-box templates provided with the Zabbix instance. These templates are not supported by IBM, however, you can use them per your own judgment. The Templates window is displayed with a list of all supported templates. 5. In Templates window, select the appropriate OS template based on your operating system. For Linux, select AMM Template OS Linux and for Windows, select AMM Template OS Windows. 6. Click Select to add this template. 7. Click Add link. The newly added template is added to the Linked templates list. 8. Click Update. Chapter 5. Working with the Zabbix UI 15

24 Remember: Features outside the scope of this document are not supported by IBM. Apply MySQL Monitoring Template to Devices IBM Cloud AMM - monitoring service provides a custom template AMM Template App MySQL. If you want to monitor MySQL, then you must install this template. Before you begin This template executes the MySQL command on the devices to collect the metrics. The command requires MySQL user and password information. Instead of passing it as a parameter of the command, create an OPTIONS file at /var/tmp/.my.cnf so the command can read the OPTIONS file for credential details. This OPTIONS file can be secured by authorized users. The script that this template uses assumes the OPTIONS file in the specified path, however, you can update the script to change the path. Sample file contents - [client] user = root password = zabbix About this task In Linux OS, support is provided to monitor MySQL Community Server v5.6.x. You cannot apply "AMM Template App MySQL" for a Windows host as support is not provided for MySQL on Windows. Procedure 1. Navigate to Configuration > Hosts. 2. Click the host name link to monitor the database. 3. Switch to Templates tab. 4. Click Select link to add a new template to the host. Note: There are many out-of-the-box templates provided with the Zabbix instance. These templates are not supported by IBM, however, you can use them in a self-supported mode. 5. Select AMM Template App MySQL from the list. 16 IBM Cloud Automated Modular Managed (AMM): monitoring services

25 6. Click Select to add this template. 7. Click Add link. Note: Similarly, you can add this template for a host on Windows OS. The AMM Template App MySQL is added to the Linked templates list. 8. Click Update. Apply Microsoft SQL Server Template to Devices IBM Cloud AMM - monitoring service provides a custom template AMM Template App Microsoft SQL Server. If you want to monitor Microsoft SQL on Windows devices, then you must install this template. The service supports all editions of Microsoft SQL Express, Enterprise, and Standard Editions. Before you begin v This template executes the Microsoft SQL command on Windows devices to collect the metrics. Before you apply the template, in the Macros tab, you must mention the user, password, and ODBC details of Microsoft SQL. Steps to include Microsoft SQL user, password, and ODBC information: 1. Navigate to Configuration > Hosts. 2. Click the host name link to monitor the database. 3. Go to the Macros tab. Chapter 5. Working with the Zabbix UI 17

26 4. Click Add to include three macros, namely {$USER}, {$PASSWORD}, and {$ODBC}. 5. Enter values for these three macros. 6. Run /monitoring/updateconfig API. For more information, see AMM_Monitoring_Service_API_Documentation.pdf. Important: Currently, support is provided only for Default Instance monitoring and Named Instance monitoring is not supported. v Ensure that the TCP/IP protocol is enabled in the Windows device. v You cannot manually create a host, so first install the agent that creates the host on Zabbix and then add the template on top of that agent. The Microsoft SQL server monitoring will not work without an agent. About this task Important: The "AMM Template App Microsoft SQL Server" can only be applied on Windows 2008 R2 and 2012 devices. Procedure 1. Navigate to Configuration > Hosts. 2. Click the host name link to monitor the database. 3. Switch to Templates tab. 4. Click Select link to add a new template to the host. Note: There are many out-of-the-box templates provided with the Zabbix instance. These templates are not supported by IBM, however, you can use them in a self-supported mode. 5. Select AMM Template App Microsoft SQL Server from the list. 6. Click Select to add this template. 18 IBM Cloud Automated Modular Managed (AMM): monitoring services

27 7. Click Add link. The AMM Template App Microsoft SQL Server is added to the Linked templates list. 8. Click Update. Apply Apache Monitoring Template to Device You must apply "AMM-Template-App-Apache" template on the device. Follow the steps in Apply MySQL Monitoring Template to Devices on page 16 section to apply the AMM-Template-App-Apache template on the device. Apply VMware Template You must apply "Template Virt VMware" template on the device. Follow the steps in Apply MySQL Monitoring Template to Devices on page 16 section to apply "Template Virt VMware" template on the device. Operating System and Base Resource Monitoring from Zabbix UI From Monitoring > Latest data page, you can monitor CPU, memory, and disk usage. Important: Ensure that either AMM Template OS Linux or AMM Template OS Windows is applied to all hosts that you want to monitor. Install the template manually if it is not already applied automatically to your host. Install the template manually if it is not already applied automatically to your host. To search for a host, enter the host name you want to administer and click Search. For advanced search, enter any of the following known values and click Filter: v Host group v Host v Application v Name An example for a Windows host latest data: Chapter 5. Working with the Zabbix UI 19

28 You can see the graphs by clicking on Graph link next to any of these parameters. These graphs are linear graphs and are available by default for any numeric value. There are also additional graphs of other types like pie-chart, barchart that are provided as part of the monitoring template. The following sections illustrate some of the graphs that can be used to view the CPU, memory, and disk statistics in a graphical way. CPU Utilization Procedure to view CPU utilization in graphical format: Procedure 1. Navigate to Monitoring > Graphs. 2. Select the appropriate Group and Host. 3. Select the value from the Graph list. For Linux, select CPU utilization and for Windows, select CPU load. 20 IBM Cloud Automated Modular Managed (AMM): monitoring services

29 Memory Usage Procedure to view memory utilization in graphical format. Procedure 1. Navigate to Monitoring > Graphs. 2. Select the appropriate Group and Host. 3. Select Memory usage from the Graph list. Disk Space Usage Procedure to view disk space usage in graphical format. Procedure 1. Navigate to Monitoring > Graphs. 2. Select the appropriate Group and Host. Chapter 5. Working with the Zabbix UI 21

30 3. Select Disk space usage / from the Graph list for Linux. For Windows, select Disk space usage <drive:>:. Configuration You must configure settings to receive alerts in the event of problems. When problem occurs, is sent to a specified user or to the users of specified groups, so set address at user level. About this task User groups allow the grouping of users both for organizational purposes and for assigning permissions to data. Permissions to monitoring data of host groups are assigned to user groups, but not to individual users. Procedure 1. Navigate to Administration > Users. 2. Select Users from the drop-down list available at the top-right corner of the screen. 3. Select the user Admin. 22 IBM Cloud Automated Modular Managed (AMM): monitoring services

31 4. In the CONFIGURATION OF USER page, go to Media tab. The Media tab contains a list of all media that are defined for the user. Media is used for sending notifications. 5. Click Add to add new media. Alert Configuration 6. Provide the following values: v Type Enter the type of media. For this sample, select . v Send to Enter the ID of the user. v When active It is prepopulated with the time from when the user is active; you can edit the value. v Use if severity Select the severity levels. The available values are Not classified, Information, Warning, Average, High, and Disaster. v Status Select Enabled from the list. 7. Click Add. An entry is added to the list in Media tab. 8. Click Update. The ID is set up and will start receiving s. Every parameter that Zabbix collects from the monitored devices is called an item. Item values are collected at regular intervals. For example, MySQL server status is an item, and its numeric value, up (1) or down (0) is collected at regular intervals. Trigger is an event that detects a particular value of the item. For example, define a trigger for MySQL server status value as 0 (down). Whenever a trigger situation happens (for example, MySQL is down), a trigger is generated in Zabbix and it is visible in the Monitoring > Triggers page. Chapter 5. Working with the Zabbix UI 23

32 However, Zabbix does not send alerts for triggers to users unless you create an action associated with that trigger. It informs Zabbix the action it has to take in case of a trigger, for example, send an . In this example, the status of MySQL server is the alert condition. MySQL server is running on a device and you have applied the "AMM Template App MySQL" to that device. Zabbix starts monitoring MySQL. Create Action You can define actions that must be performed in case of a trigger. For the purpose of this illustration, actions related to MySQL are used. About this task You must apply the AMM Template APP MySQL. To apply template for MySQL, see section Database Monitoring on page 27. Procedure 1. Navigate to Configuration > Actions. 2. In CONFIGURATION OF ACTIONS, click Create action to create a new action. 3. Enter the following values in the Action tab: v Name Enter the name of the new action. v Default subject - The default subject of the . v Default message - The default message of the . v Recovery message - Select this if you want an message after the recovery of the trigger situation. v Enabled - Select this to enable the action. In this example, an additional condition is set for SQL status. 4. Switch to Condition tab. 24 IBM Cloud Automated Modular Managed (AMM): monitoring services

33 Important: Define an alert condition so that any alert generated for MySQL down status triggers an notification. The alert is not specific to the current device that is shown in this example, but it also applies to other devices or any new device where MySQL monitoring gets configured. 5. Change the condition at the top to AND. 6. In New condition, select Trigger name from the list and enter AMM Template App MySQL: MySQL is down. 7. Click Add link. 8. Open Operations tab. 9. Click Update. 10. Select Templates for Group and Template App MySQL for Host. 11. Click trigger MySQL is down to add it to the list. 12. Switch to Operations tab to define the notification operation. 13. Click New link. 14. Select Operation type as Send message. Chapter 5. Working with the Zabbix UI 25

34 15. Click Add link in Send to Users section. Note: You can select one or more users. You can also configure the Send to user groups to send messages to a group. 16. Select Admin user and click Select to add it to the list. 17. Select from the list in Send only to section. 18. Click Update link. The sending operation is added. 19. Click Update to save the changes. 26 IBM Cloud Automated Modular Managed (AMM): monitoring services

35 Enable/Disable alerts When MySQL service on a device goes down, you will receive an notification. After alerts (Actions) are configured in Zabbix dashboard, they are enabled by default and you will keep getting s in case of alert conditions. However, you must also disable such alerts in various situations. For example, when the device or MySQL service is under maintenance, it must be stopped and notification must be disabled to avoid false alarm. Procedure 1. Navigate to Configuration > Actions. Database Monitoring 2. Click Enabled link to disable the notification. Click Disabled link to enable it again. IBM Cloud AMM - monitoring service supports MySQL database monitoring. The template provides basic parameters of MySQL instance running on the device. You must have already applied "AMM-Template-App-MySQL" template. Note: In Linux OS, support is provided to monitor MySQL Community Server v5.6.x. Important: You cannot apply "AMM-Template-App-MySQL" for a Windows host as support is not provided for MySQL on Windows. Chapter 5. Working with the Zabbix UI 27

36 Viewing MySQL Monitoring Data on Dashboard You can view the metrics that are collected form the MySQL instance. Procedure 1. Navigate to Monitoring > Latest data. 2. Select the device from right hand side drop-down list. You will see the items collected by the monitoring agent. Triggers Based on MySQL Service Status The template provided with IBM Cloud AMM - monitoring service has a defined trigger. This trigger gets generated when MySQL service goes down. If Zabbix has collected the MySQL status as 1, then it implies that MySQL is running. If MySQL service goes down, the value changes to 0 (stopped), and a trigger is generated. To see the trigger, navigate to Monitoring > Triggers. Configuring alerts You must define alerts for the triggers. See section Alert Configuration on page 23 to define alerts for the triggers, which are available in MySQL monitoring template. You can additionally define your own triggers and configure alerts for them. 28 IBM Cloud Automated Modular Managed (AMM): monitoring services

37 Apache Web Server Monitoring IBM Cloud AMM - monitoring service supports monitoring of Apache web server. The template provides basic parameters of Apache web server instance that runs on the device. Prerequisites v You must have already applied AMM-Template-App-Apache template. v Make the following changes in httpd.conf file for the Apache template to work: 1. Make sure to allow the server status reports that are generated by mod_status: <Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from ::1 localhost </Location> 2. Make sure to allow remote server configuration reports: <Location /server-info> SetHandler server-info Order deny,allow Deny from all Allow from ::1 localhost </Location> 3. Restart the Apache service for changes in the configuration to take effect - service httpd restart Viewing Apache monitoring data on dashboard To view the metrics that are collected form the Apache instance, perform this procedure. Procedure 1. Navigate through Monitoring > Latest data. 2. Select the device from right-hand side dropdown. 3. Expand Apache to see the items collected by the monitoring agent. Triggers Based on Apache Service Status The template that is provided with IBM Cloud AMM - monitoring service has a defined trigger. This trigger gets generated when Apache service goes down. If Chapter 5. Working with the Zabbix UI 29

38 Zabbix collects 0 as Apache status, then it implies that Apache is running. If Apache service goes down, the value changes to 1 (stopped), and a trigger is generated. To see the trigger, navigate to Monitoring > Triggers. VMware Monitoring For prerequisites, see Chapter 4, Setting Up VMware Hosts for Monitoring, on page 11. Viewing Hypervisor Data on Dashboard Procedure to view hypervisor data on dashboard. Procedure 1. In the Service UI, navigate through Monitoring > Latest data. 2. Select the device from right hand side drop-down. To discover the devices, see Run Discovery Manually on page IBM Cloud Automated Modular Managed (AMM): monitoring services

39 SNMP Monitoring As a prerequisites, enable SNMP on the device that must be monitored. Important: The number of SNMP devices being monitored will be metered and charged at the same rate as monitoring of a SoftLayer device. SNMP Monitoring for RHEL Device The IBM Cloud AMM - monitoring service supports SNMP monitoring for RHEL device. Before you begin v Before you enable SNMP, log in to RHEL device and install the following utils: yum install net-snmp-utils yum install net-snmp yum install net-tools Configure the snmpd.conf to point to your Linux device: - Run the command vi /etc/snmp/snmpd.conf. - Locate the line com2sec notconfiguser default public and change it to com2sec read-only <IP of the zabbix instance> public Note: In case of private IP, add the DNS name instead of the IP. For example, amm-qa-007.mms.ibmcloud.com instead of Locate the following lines: # groupname securitymodel securityname group notconfiggroup v1 notconfiguser group notconfiggroup v2c notconfiguser Change the lines as follows with read-only: # groupname securitymodel securityname group notconfiggroup v1 read-only group notconfiggroup v2c read-only - Locate the following lines and comment them with #: view systemview included view systemview included Chapter 5. Working with the Zabbix UI 31

40 Add a new line as follows: view all included Locate the following lines: # group context sec.model sec.level prefix read write notif access notconfiggroup any noauth exact systemview none none Change the "systemview" to "all": # group context sec.model sec.level prefix read write notif access notconfiggroup any noauth exact all none none - After you configure the file, press Esc key and then : wq! to save. v Use these step to enable SNMP and start SNMP: For RHEL 5 and 6, run these commands: chkconfig snmpd on service snmpd start For RHEL 7 and later versions, run these commands: systemctl enable snmpd systemctl start snmpd Note: Every time you make changes to the snmpd.conf file, restart snmpd service for the changes to take effect. Procedure 1. Install SNMP enabled Windows or Linux agents manually or using IS. 2. Log in to the Zabbix UI. 3. In the Host > Templates tab, add AMM Template SNMP Agent OS Linux. For steps to add templates, see Applying Templates on page Click Save. If the SNMP host record changes to green, then it signifies that the host is discovered and connected. 5. Go to Monitoring > Latest Data and enter the host details. 6. Click Filter. As an example, to view the Device uptime details, click Graph link. 32 IBM Cloud Automated Modular Managed (AMM): monitoring services

41 SNMP Monitoring for Windows 2012 Device Before you begin 1. Connect to the Windows device. 2. Click Windows Key > Administrative Tools > Services. Note: If the list contains SNMP Service (already installed), you can skip Steps 3 to Click on Windows Key > Control Panel, select Turn Windows features on or off. 4. Select the Role-based or feature-based installation and click Next. 5. In the Select a server from the server pool and Server Pool section, select the server where you want to install SNMP. 6. Click Next. 7. In the Select server roles, click Next. 8. In Select features > Features, scroll and select SNMP Service. 9. Click Next. 10. In the Confirmation page, click Install. After the installation is complete, go to Services and configure SNMP. You may notice that there are several familiar tabs such as Agent and Traps missing. These require an additional installation. 11. Go back into Control Panel > Turn Windows features on or off 12. Click Next until you get back to the Select feature page. 13. In the Select features, expand Remote Server Administrator Tools > Feature Administration Tools. 14. Select SNMP Tools and click Next. 15. In the Confirmation page, click Install. 16. Reboot the server. The SNMP Service Properties of SNMP Trap will include Agent, Traps, and Security tabs. Chapter 5. Working with the Zabbix UI 33

42 17. Open the Security tab. 18. In the Accepted community names section, click Add. 19. In the SNMP Service Configuration, select READ_ONLY option for Community rights and select Community Name as public. 20. Click OK. 21. In the Security tab, select Accept SNMP packets from these hosts or Accept SNMP packets from any host. 22. If you select Accept SNMP packets from these hosts, then add IP address of Zabbix so that the Windows device can accept SNMP packets from Zabbix. Note: In case of private IP, add the DNS name instead of the IP. For example, amm-qa-007.mms.ibmcloud.com instead of IBM Cloud Automated Modular Managed (AMM): monitoring services

43 23. Now, install SNMP enabled Windows agents manually or using IS. Procedure 1. Log in to Zabbix and in the Host > Templates tab, add AMM Template SNMP Agent OS Windows. For steps to add templates, see Applying Templates on page Click Save. The SNMP icon of the added host record turns green in Zabbix. It indicates that the host is discovered and is connected. 3. Go to Monitoring > Latest Data and filter for the host. For example, Used Disk Space on Physical Memory, Device Uptime, Incoming traffic on interface Citrix PV Network Adapter, and Outgoing traffic on interface Citrix PV Network Adapter are shown in this section for illustration. 4. Click Graph link of Used Disk Space on Physical Memory. Click Graph link of Device Uptime. Chapter 5. Working with the Zabbix UI 35

44 Click Graph link for Incoming traffic on interface Citrix PV Network Adapter. Click Graph link for Outgoing traffic on interface Citrix PV Network Adapter. SNMP Only Monitoring If you opt for SNMP only monitoring, you do not have to install the agent on top of the device. Instead, you can directly add host from the Zabbix UI. About this task You must not add "AMM Template OS Linux" and "AMM Template SNMP Agent OS Linux" (in case of RHEL VM) templates for both agent and SNMP monitoring. Both these templates contain an identical item key, that is, 'Device name', which results in an error due to item key conflict. Use AMM Template SNMP Only OS 36 IBM Cloud Automated Modular Managed (AMM): monitoring services

45 Linux for SNMP Only monitoring. For Agent and SNMP monitoring, use AMM Template SNMP Agent OS Linux. Likewise, the same is applicable for Windows SNMP templates as well. Note: The steps to create a host in Zabbix is applicable only for SNMP Only Monitoring. You can configure SNMP on an already existing agent, but in case of SNMP Only Monitoring, you cannot include agent monitoring at a later time. However, you can remove the host entry in Zabbix and install the agent. Note: The steps to create host in Zabbix is applicable only for SNMP Only Monitoring. Procedure 1. Log in to Zabbix UI. 2. Go to Configuration > Hosts. 3. Click Create Host. 4. Enter the following details in Host tab: v Host name Enter the name as FQDN (Fully Qualified Domain Name) of the ESX server as on the Softlayer. v Visible name Enter the same name as host name. v Groups Add host to the required group. (Linux Servers/Windows Servers). v SNMP interfaces (IP address) Give IP address of the device to be monitored. IP of the RHEL/Windows device. 5. In the Templates tab, add the appropriate OS template AMM Template SNMP Agent OS Linux" (in case of RHEL device) or AMM Template SNMP OS Windows (in case of Windows device). 6. Save the record. Administering the Monitoring Agent This section gives the details on various CLI administrative actions that can be performed on the Zabbix agent(s). To login (PuTTY or any other SSH / SFTP connection software) to the monitored device, use the IP address and password that is available in your SoftLayer account. Run the commands mentioned in this section from the shell. Restart Zabbix Agent To restart Zabbix agent, perform stop and start of the agent processes. Always restart the agent whenever there are changes to the agent configuration files. For more information, see For example, when you change the MySQL password. Start and Stop Zabbix agent in Linux OS The commands to start and stop Zabbix agent in Linux OS. Stop Zabbix agent: /etc/init.d/zabbix-agent stop Start Zabbix agent: /etc/init.d/zabbix-agent start Chapter 5. Working with the Zabbix UI 37