NetIQ AppManager for Self Monitoring (AM Health) Management Guide

Transcription

1 NetIQ AppManager for Self Monitoring (AM Health) Management Guide September

2 Legal Notice THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU. For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions. This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data. This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time. U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R (for Department of Defense (DOD) acquisitions) and 48 C.F.R and (for non-dod acquisitions), the government s rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement NetIQ Corporation. All Rights Reserved. For information about NetIQ trademarks, see

3 Contents About this Book and the Library 5 About NetIQ Corporation 7 1 Introducing AppManager for Self Monitoring 9 2 Installing AppManager for Self Monitoring System Requirements Installing the Module Silently Installing the Module Configuring Security Manager for AM Health Discovering AppManager Resources for Windows Discovering AppManager Resources for UNIX and Linux Servers Upgrading Knowledge Script Jobs AM Health Knowledge Scripts AgentDown CCComponentsHealth HeartbeatUNIX HeartbeatWin QDBComponentsHealth TaskSchedulerHealth Recommended Knowledge Script Groups Contents 3

4 4 NetIQ AppManager for Self Monitoring (AM Health) Management Guide

5 About this Book and the Library The NetIQ AppManager product (AppManager) is a comprehensive solution for managing, diagnosing, and analyzing performance, availability, and health for a broad spectrum of operating environments, applications, services, and server hardware. AppManager Self Monitoring provides system administrators with a central, easy-to-use console to view critical server and application resources across the enterprise. With AppManager Self Monitoring, administrative staff can monitor computer and application resources, check for potential problems, initiate responsive actions, automate routine tasks, and gather performance data for realtime and historical reporting and analysis. Intended Audience This guide provides information for individuals responsible for installing an AppManager module and monitoring specific applications with AppManager. Other Information in the Library The library provides the following information resources: Installation Guide for AppManager Provides complete information about AppManager pre-installation requirements and step-bystep installation procedures for all AppManager components. User Guide for AppManager Control Center Provides complete information about managing groups of computers, including running jobs, responding to events, creating reports, and working with Control Center. A separate guide is available for the AppManager Operator Console. Administrator Guide for AppManager Provides information about maintaining an AppManager management site, managing security, using scripts to handle AppManager tasks, and leveraging advanced configuration options. Upgrade and Migration Guide for AppManager Provides complete information about how to upgrade from a previous version of AppManager. Management guides Provide information about installing and monitoring specific applications with AppManager. Help Provides context-sensitive information and step-by-step guidance for common tasks, as well as definitions for each field on each window. The AppManager Self Monitoring library is available in Adobe Acrobat (PDF) format from the AppManager Documentation page of the NetIQ website. About this Book and the Library 5

6 6 NetIQ AppManager for Self Monitoring (AM Health) Management Guide

7 About NetIQ Corporation We are a global, enterprise software company, with a focus on the three persistent challenges in your environment: Change, complexity and risk and how we can help you control them. Our Viewpoint Adapting to change and managing complexity and risk are nothing new In fact, of all the challenges you face, these are perhaps the most prominent variables that deny you the control you need to securely measure, monitor, and manage your physical, virtual, and cloud computing environments. Enabling critical business services, better and faster We believe that providing as much control as possible to IT organizations is the only way to enable timelier and cost effective delivery of services. Persistent pressures like change and complexity will only continue to increase as organizations continue to change and the technologies needed to manage them become inherently more complex. Our Philosophy Selling intelligent solutions, not just software In order to provide reliable control, we first make sure we understand the real-world scenarios in which IT organizations like yours operate day in and day out. That's the only way we can develop practical, intelligent IT solutions that successfully yield proven, measurable results. And that's so much more rewarding than simply selling software. Driving your success is our passion We place your success at the heart of how we do business. From product inception to deployment, we understand that you need IT solutions that work well and integrate seamlessly with your existing investments; you need ongoing support and training post-deployment; and you need someone that is truly easy to work with for a change. Ultimately, when you succeed, we all succeed. Our Solutions Identity & Access Governance Access Management Security Management Systems & Application Management Workload Management Service Management About NetIQ Corporation 7

8 Contacting Sales Support For questions about products, pricing, and capabilities, contact your local partner. If you cannot contact your partner, contact our Sales Support team. Worldwide: United States and Canada: Website: Contacting Technical Support For specific product issues, contact our Technical Support team. Worldwide: North and South America: Europe, Middle East, and Africa: +353 (0) Website: Contacting Documentation Support Our goal is to provide documentation that meets your needs. The documentation for this product is available on the NetIQ website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at documentation. You can also Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you. Contacting the Online User Community NetIQ Communities, the NetIQ online community, is a collaborative network connecting you to your peers and NetIQ experts. By providing more immediate information, useful links to helpful resources, and access to NetIQ experts, NetIQ Communities helps ensure you are mastering the knowledge you need to realize the full potential of IT investments upon which you rely. For more information, visit community.netiq.com. 8 NetIQ AppManager for Self Monitoring (AM Health) Management Guide

9 1 1Introducing AppManager for Self Monitoring The AppManager Self Monitoring module, also known as AM Health, provides Knowledge Scripts for monitoring the health and availability of AppManager components. You can use the AM Health module to monitor the following AppManager components and features: Health and availability of Microsoft SQL Server resources associated with the AppManager repository (QDB) and the management server. These resources include SQL Server services, management server services, and SQL Server queries. Health and availability of Microsoft SQL Server resources associated with AppManager Control Center components. These components include the Cache Manager, the Command Queue Service (CQS), deployment services, and the Control Center repository (NQCCDB). Heartbeat of AppManager Windows agent computers. A heartbeat is a periodic signal generated by an AppManager agent computer to indicate that it is still running. If an AppManager agent fails to send either data or an event to the QDB within the specified grace period, AppManager assumes that the agent is offline and generates a corresponding event. Heartbeat of AppManager UNIX agent computers. Introducing AppManager for Self Monitoring 9

10 10 NetIQ AppManager for Self Monitoring (AM Health) Management Guide

11 2 2Installing AppManager for Self Monitoring This chapter provides installation instructions and describes system requirements for AppManager for Self Monitoring (AM Health). This chapter assumes you have AppManager installed. For more information about installing AppManager or about AppManager system requirements, see the Installation Guide for AppManager, which is available on the AppManager Documentation page. 2.1 System Requirements For the latest information about supported software versions and the availability of module updates, visit the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below. AppManager Self Monitoring has the following system requirements: Software/Hardware NetIQ AppManager installed on the AppManager repository (QDB) computer and on all console computers NetIQ AppManager for Microsoft Windows module installed on the AppManager agent computers Microsoft.NET Framework installed on the AppManager agent computers Version or later or later 2.0 or Installing the Module Run the module installer only once on any Windows computer. The module installer automatically identifies and updates all relevant AppManager components on a computer. Access the AM70-AMHealth-8.2.x.0.msi module installer from the AM70_AMHealth_8.2.x.0 selfextracting installation package on the AppManager Module Upgrades & Trials page. You can install the Knowledge Scripts and the Analysis Center reports into local or remote AppManager repositories (QDBs). The module installer installs Knowledge Scripts for each module directly into the QDB instead of installing the scripts in the \AppManager\qdb\kp folder as in previous releases of AppManager. To install the module manually: 1 Double-click the module installer.msi file. 2 Accept the license agreement. 3 Run the module installer on all console computers to install the Help and console extensions. Installing AppManager for Self Monitoring 11

12 4 To install the Knowledge Scripts into the QDB: 4a Select Install Knowledge Scripts to install the repository components, including the Knowledge Scripts. 4b Specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name. 5 Run the module installer only for the primary QDB. Control Center automatically replicates this module to secondary QDBs. 6 (Conditional) If the service account does not have sufficient privileges to run Discovery_AMHealth, set up SQL authentication with AppManager Security Manager. For more information, see Section 2.4, Configuring Security Manager for AM Health, on page (Conditional) If you have not discovered AM Health Windows resources, run the Discovery_AMHealth Knowledge Script on all Windows agent computers where you installed the module. For more information, see Section 2.5, Discovering AppManager Resources for Windows, on page (Conditional) If you have not discovered AM Health UNIX or Linux resources, run the Discovery_AMHealthUNIX Knowledge Script on all UNIX or Linux agent computers where you installed the module. For more information, see Section 2.6, Discovering AppManager Resources for UNIX and Linux Servers, on page To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see Section 2.7, Upgrading Knowledge Script Jobs, on page 15. After the installation has completed, the AMHealth_Install.log file, located in the \NetIQ\Temp\NetIQ_Debug\<ServerName> folder, lists any problems that occurred. 2.3 Silently Installing the Module To silently (without user intervention) install a module using the default settings, run the following command from the folder in which you saved the module installer: msiexec.exe /i "AM70-AMHealth-8.2.x.0.msi" /qn where x.x is the actual version number of the module installer. To create a log file that describes the operations of the module installer, add the following flag to the command noted above: /L* "AM70-AMHealth-8.2.x.0.msi.log" The log file is created in the directory in which you saved the module installer. NOTE: To perform a silent install on an AppManager agent running Windows Server 2008 R2 or Windows Server 2012, open a command prompt at the administrative level and select Run as administrator before you run the silent install command listed above. To silently install the module on a remote AppManager repository, you can use Windows authentication or SQL authentication. Windows authentication: AM70-AMHealth-8.2.x.0.msi /qn MO_B_QDBINSTALL=1 MO_B_SQLSVR_WINAUTH=1 MO_SQLSVR_NAME=SQLServerName MO_QDBNAME=AM-RepositoryName 12 NetIQ AppManager for Self Monitoring (AM Health) Management Guide

13 SQL authentication: AM70-AMHealth-8.2.x.0.msi /qn MO_B_QDBINSTALL=1 MO_B_SQLSVR_WINAUTH=0 MO_SQLSVR_USER=SQLLogin MO_SQLSVR_PWD=SQLLoginPassword MO_SQLSVR_NAME=SQLServerName MO_QDBNAME=AM-RepositoryName 2.4 Configuring Security Manager for AM Health If the service account does not have sufficient privileges, before running the Knowledge Script, set up SQL authentication with AppManager Security Manager. On the Custom tab in Security Manager, complete the following fields: Field Label Description sql$<agent server name> For example, if your agent server name is SERVER1TEST, you would type sql$server1test. Sub-label Value 1 Value 2 Value 3 Extended application support SQL user name that exists in the QDB. Password for the user entered in the Sub-Label field. Leave this field blank. Leave this field blank. Required field. Encrypts the user name and password in Security Manager. Do not leave this option unselected. NOTE: To discover or monitor the QDB and CCDB roles on a cluster instance, you must configure Security Manager on all cluster nodes. When you want to discover the management server, use the SQL user name used above for the SQL Server login parameter of the Discovery_AMHealth Knowledge Script. For more information about discovering AM Health resources, see Section 2.5, Discovering AppManager Resources for Windows, on page 14. If an agent is not installed on the QDB, and the NetIQ Client Resource Monitor (netiqmc) service accounts on the management server do not have sufficient rights to access the QDB, configure the NetIQ services with a Windows account that has access to the QDB. Otherwise, configure the Discovery_AMHealth Knowledge Script to use SQL authentication by typing a SQL user name in the SQL Server login parameter for Discovery_AMHealth. For example, sql$<management server name>. For example, if your management server name is SERVER1TEST, you would type sql$server1test. If an agent is not installed on the Control Center repository (NQCCDB), and the netiqmc service accounts on the NetIQ Command Queue Server do not have sufficient rights to access the NQCCDB, configure the NetIQ service accounts with a Windows account that has access to the NQCCDB. Otherwise, configure the Discovery_AMHealth Knowledge Script to use SQL authentication. For example, sql$<command queue server>. For example, if your command queue server name is SERVER1TEST, you would type sql$server1test. Installing AppManager for Self Monitoring 13

14 If an agent is installed on QDB or NQCCDB, and the netiqmc service accounts on the NetIQ Command Queue Server do not have sufficient rights to access QDB or NQCCDB, you can configure SQL user of the agent in AppManager Security Manager to monitor the health and availability of AppManager components. For example, sql$<agent server name>. For example, if your agent server name is SERVER1TEST, you would type sql$server1test. You can also use the AppManager Security Manager configuration listed above to monitor the health of a management server that is in an untrusted domain from your AppManager installation. Use a SQL Server user to allow the AM Health Knowledge Scripts on the management server in the untrusted domain to communicate with the QDB on the SQL Server. You cannot use Windows authentication, because the SQL Server will not be aware of any users that belong to the untrusted domain. 2.5 Discovering AppManager Resources for Windows Use the Discovery_AMHealth Knowledge Script to discover AppManager and Control Center resources installed on Windows servers. This Knowledge Script returns information about successful and failed discoveries, and it raises events to notify you of errors. Run the Discovery_AMHealth script on computers with the one or more of the following AppManager components: AppManager repository (QDB), management server, Cache Manager, Command Queue Service (CQS), deployment service, AppManager managed client, Control Center repository (NQCCDB), and Task Scheduler service. In a clustered environment, the Discovery_AMHealth script discovers only QDB and CCDB roles. For more information about the setup of the AMHealth Module s AMHealth_QDBComponentsHealth Knowledge Script in a clustered environment, contact NetIQ Technical Support. By default, this script is only run once for each computer. Set the following parameters as needed: Parameter Event Notification Raise an event if discovery succeeds? Event severity when discovery succeeds Raise event if discovery fails? Event severity when discovery fails Event severity when job fails Select Yes to raise an event when discovery succeeds. The default is unselected. Set the event severity level, from 1 to 40, to reflect the importance of an event in which when the discovery succeeds. The default is 25. Select Yes to raise an event when discovery fails. The default is Yes. Set the event severity level, from 1 to 40, to reflect the importance of an event in which the discovery fails. The default is 5. Set the severity level, from 1 to 40, to indicate the importance of an event in which the Discovery_AMHealth job itself fails. The default is NetIQ AppManager for Self Monitoring (AM Health) Management Guide

15 Parameter SQL Server login Specify the SQL user name required for access to the AppManager repository (QDB). Leave this field blank to use Windows authentication. NOTE: If you want to use a specific SQL Server login account, use Security Manager to update the AppManager repository with the SQL Server logins that you want to use. For more information, see Section 2.4, Configuring Security Manager for AM Health, on page Discovering AppManager Resources for UNIX and Linux Servers Use the Discovery_AMHealthUNIX Knowledge Script to discover AppManager resources installed on UNIX and Linux servers. This Knowledge Script returns information about successful, failed, and partial discoveries, and it raises events to notify you of errors. Run the Discovery_AMHealthUNIX script on AppManager UNIX agents. By default, this script runs once for each computer. Set the following parameters as needed: Parameter Raise event if discovery succeeds? Event severity when discovery succeeds Event severity when discovery fails Event severity when discovery partially succeeds Set to y to raise an event when discovery succeeds. The default is unselected. Set the event severity level, from 1 to 40, to reflect the importance of an event in which discovery succeeds. The default is 25. Set the event severity level, from 1 to 40, to reflect the importance when the discovery fails. The default is 5. Set the event severity level, from 1 to 40, to reflect the importance when the discovery partially succeeds. This type of situation usually occurs when the target computer does not have all the prerequisites installed. The default is Upgrading Knowledge Script Jobs If you are using AppManager 8.x or later, the module upgrade process now retains any changes you might have made to the parameter settings for the Knowledge Scripts in the previous version of this module. Before AppManager 8.x, the module upgrade process overwrote any settings you might have made, changing the settings back to the module defaults. As a result, if this module includes any changes to the default values for any Knowledge Script parameter, the module upgrade process ignores those changes and retains all parameter values that you updated. Unless you review the management guide or the online Help for that Knowledge Script, you will not know about any changes to default parameter values that came with this release. Installing AppManager for Self Monitoring 15

16 You can push the changes for updated scripts to running Knowledge Script jobs in one of the following ways: Use the AMAdmin_UpgradeJobs Knowledge Script. Use the Properties Propagation feature Running AMAdmin_UpgradeJobs The AMAdmin_UpgradeJobs Knowledge Script can push changes to running Knowledge Script jobs. Your AppManager repository (QDB) must be at version 7.0 or later. Upgrading jobs to use the most recent script version allows the jobs to take advantage of the latest script logic while maintaining existing parameter values for the job. For more information, see the Help for the AMAdmin_UpgradeJobs Knowledge Script Propagating Knowledge Script Changes You can propagate script changes to jobs that are running and to Knowledge Script Groups, including recommended Knowledge Script Groups and renamed Knowledge Scripts. Before propagating script changes, verify that the script parameters are set to your specifications. You might need to appropriately set new parameters for your environment or application. If you are not using AppManager 8.x or later, customized script parameters might have reverted to default parameters during the installation of the module. You can choose to propagate only properties (specified in the Schedule and Values tabs), only the script (which is the logic of the Knowledge Script), or both. Unless you know specifically that changes affect only the script logic, you should propagate the properties and the script. For more information about propagating Knowledge Script changes, see the Running Monitoring Jobs chapter of the Control Center User Guide for AppManager Propagating Changes to Ad Hoc Jobs or Knowledge Script Groups You can propagate the properties and the logic (script) of a Knowledge Script to ad hoc jobs started by that Knowledge Script. Corresponding jobs are stopped and restarted with the Knowledge Script changes. You can also propagate the properties and logic of a Knowledge Script to corresponding Knowledge Script Group members. After you propagate script changes to Knowledge Script Group members, you can propagate the updated Knowledge Script Group members to associated running jobs. Any monitoring jobs started by a Knowledge Script Group member are restarted with the job properties of the Knowledge Script Group member. To propagate changes to ad hoc Knowledge Script jobs or Knowledge Script Groups: 1 In the Knowledge Script view, select the Knowledge Script or Knowledge Script Group for which you want to propagate changes. 2 Right-click the script or group and select Properties propagation > Ad Hoc Jobs. 16 NetIQ AppManager for Self Monitoring (AM Health) Management Guide

17 3 Select the components of the Knowledge Script that you want to propagate to associated ad hoc jobs or groups and click OK: Select Script Properties To propagate The logic of the Knowledge Script. Values from the Knowledge Script Schedule and Values tabs, such as schedule, monitoring values, actions, and advanced options. If you are using AppManager 8.x or later, the module upgrade process now retains any changes you might have made to the parameter settings for the Knowledge Scripts in the previous version of this module. Installing AppManager for Self Monitoring 17

18 18 NetIQ AppManager for Self Monitoring (AM Health) Management Guide

19 3 3AM Health Knowledge Scripts The AppManager Self Monitoring module, also known as AM Health, provides Knowledge Scripts for monitoring the health and availability of AppManager components. From the Knowledge Script view of Control Center, you can access more information about any NetIQ-supported Knowledge Script by selecting it and clicking Help. In the Operator Console, click any Knowledge Script in the Knowledge Script pane and press F1. Knowledge Script AgentDown CCComponentsHealth HeartbeatUNIX HeartbeatWin TaskSchedulerHealth QDBComponentsHealth Recommended Knowledge Script Groups What It Does Monitors the health of AppManager agents and raises events when agents are down or unavailable. Monitors the health and availability of SQL Server resources associated with Control Center components. Monitors the AppManager agent heartbeat on a UNIX or Linux server. Also monitors Knowledge Script job run time against the job schedule and against a user-defined maximum run time. Monitors the AppManager agent heartbeat in a Microsoft Windows environment. Monitors the health status of Task Scheduler that schedules SQL jobs for QDB and NQCCDB. Monitors the health and availability of SQL Server resources associated with the AppManager repository (QDB) and the management server. Perform essential monitoring of AppManager components. These groups include AMHealth_HealthCheckAMAgentComponents and AMHealth_HealthCheckAMCoreComponents 3.1 AgentDown Use this Knowledge Script to monitor the health of AppManager agents, raise events when agents are down or unavailable, and generate actions as appropriate. This script does not raise events when AppManager agents are up (running) and available. You can set the event severity for an individual agent, or you can override the severity with this script to specify one severity for any agent with issues. This script complements the AMHealth_HeartbeatWin and AMHealth_HeartbeatUNIX Knowledge Scripts, but it is different in the following important ways: Run the AMHealth_AgentDown Knowledge Script on management servers. This script queries information from the AppManager repository (QDB) to obtain agent status, which is populated by the AMHealth_Heartbeat jobs. As a result, you must run AMHealth_Heartbeat jobs on your AM Health Knowledge Scripts 19

20 agents as well as run an AMHealth_AgentDown job on your management server. One AgentDown job can monitor all agents for which the heartbeat is running. The AMHealth_AgentDown script supports the execution of actions. Run the relevant AMHealth_HeartBeat Knowledge Scripts on the agents you wish to monitor. Select Yes for either the Raise an event if the agent heartbeat fails? parameter or the Generate heartbeat data? parameter, or select both parameters. The AMHealth_Heartbeat scripts do not support the execution of actions. You can run this script on multiple management servers for redundancy. In this situation, each AMHealth_AgentDown job raises duplicate events and generates duplicate actions. If you stop and restart AMHealth_HeartbeatWin and AMHealth_HeartbeatUNIX jobs, the AMHealth_AgentDown job might raise duplicate events Prerequisites AppManager version or later on the QDB and management server AppManager version 8.0 or later on the AppManager agent AMHealth version or later on the QDB and all console computers Configuring Security Manager for AMHealth_AgentDown The AMHealth_AgentDown Knowledge Script requires credentials to connect to the AppManager Repository (QDB). If the QDB uses SQL authentication, create the following entry in Security Manager on the Custom tab: Field Label Sub-label Value 1 Value 2 Value 3 Extended application support Description AMH$SQL SQL user name with authority to access the QDB. SQL password for the user name entered in the Sub-Label field. Leave this field blank. Leave this field blank. Encrypts the user name and password in Security Manager. This option must be selected Resource Objects Management server Default Schedule The default interval for this script is every 5 minutes Setting Parameter Values Set the following parameters as needed: 20 NetIQ AppManager for Self Monitoring (AM Health) Management Guide

21 Parameter General Settings Job Failure Notification Raise event if job fails unexpectedly? Event severity when job fails unexpectedly Select Yes to raise an event if the AMHealth_AgentDown job fails unexpectedly. The default is Yes. an event that is raised when the job fails unexpectedly. The default is 5. Additional Settings Event Details Event detail format Select the format in which you want to display the event detail. You can select from HTML Table or Plain Text. The default is HTML Table. Regardless of what you enter for this parameter, if the Action_SMTPMail action Knowledge Script is associated with an AMHealth_AgentDown job, the displays in plain text. Knowledge Script Settings Always consolidate events? Select Yes to raise a single event for all down agents, regardless of how many agents are down. The default is Yes. Select No to use the Raise consolidated event if X percent of agents are down setting in Control Center for determining whether to raise a single event for all down agents, or one event per down agent. You can edit the Health Check settings in Control Center by clicking Options on the Main tab, and then clicking Health Check. SQL logon Specify the SQL Server user name required for access to the AppManager repository (QDB). This setting requires an entry in AppManager Security Manager, as described in Configuring Security Manager for AMHealth_AgentDown on page 20. Leave this field blank for Windows Authentication. Event Settings AM Health Knowledge Scripts 21

22 Parameter Override agent down severity? Select Yes to use this script to specify the event severity when an agent is down. If you select No, AppManager uses the event severity for a down agent that is specified by the AMHealth_HeartbeatWin and AMHealth_HeartbeatUNIX Knowledge Scripts. The default is Yes. To prevent the duplication of agent-down events generated by both the AMHealth_Heartbeat and AMHealth_AgentDown jobs, select Yes and set the Severity for override parameter in this script to 40. Next, choose one of the following options: In the Operator Console, open the File menu and select Preferences. On the Repository tab, click Event. Select Automatically close event when severity is greater than X and set it to 39. Using this option, events raised by AgentDown immediately go to Closed state, but actions are still executed. On the Management Server, open the registry and navigate to \SOFTWARE\..\NetIQ\AppManager\4.0\NetIQmc\Config, and set the NoEventSev registry key to 40. Then stop and restart the NetIQMC service. With this option, the AMHealth_AgentDown job does not raise events, but the script still executes actions. Severity for override an event when an agent is detected as being down or unavailable. This parameter is ignored if you do not select the Override agent down severity? parameter. The default is CCComponentsHealth Use this Knowledge Script to monitor the health and availability of Microsoft SQL Server resources associated with AppManager Control Center components. These components include the Cache Manager, the Command Queue Service (CQS), deployment services, and the Control Center repository (NQCCDB). This script monitors the percentage of database space and log space used, the amount of time required for a SQL command or query to execute, and the status of AppManager scheduled tasks, which are SQL jobs operating on the NQCCDB. This script can restart a service or job that is down. If the NQCCDB does not have an AppManager agent installed on it, Discovery_AMHealth discovers the NQCCDB components on the server running the Command Queue Service. As a result, the service and database monitoring parameters for this script run remotely. In this situation, you must have sufficient privileges on the service account for the NetIQMC service on the server running the Command Queue Service so that the service account can remotely access the SQL Server service on the NQCCDB to obtain its status. If the account does not have proper privileges, the script will be unable to access the service status and will report that the SQL Server service is down even when it is not. If you do not have sufficient access for the service account for the NetIQMC service, deselect the Raise an event if SQL Server services are down and Restart SQL Server services that stop unexpectedly parameters in this script to avoid raising unnecessary events. This script raises events for the following situations: SQL Server services are down or have been restarted. SQL jobs are disabled, missing, or have failed. 22 NetIQ AppManager for Self Monitoring (AM Health) Management Guide

23 The CQS is down or is not connected to the Control Center repository. Control Center Cache Manager errors occur. SQL Server queries against the NQCCDB take too long to process. Deployment services are down. Database or log space is low, and there is insufficient disk space for further growth. If you do not have an agent installed on the NQCCDB server, the repository component gets discovered on the CQS. If you try to remotely monitor the NQCCDB from the CQS using the CCComponentsHealth script, the script will not be able to obtain the disk information remotely. As a result, if the repository component is monitored remotely from the CQS by the CCComponentsHealth script, the following NQCCDB component monitoring parameters under the SQL Server File Size and Growth Settings Monitoring Event Notification Knowledge Script section will not be available: Raise an event if SQL Server maximum file size exceeds available disk space? Raise an event if insufficient space available for further file growth? Resource Objects Cache Manager CQS Deployment services Control Center repository Default Schedule The default interval for this script is every 30 minutes Setting Parameter Values Set the following parameters as needed: Parameter General Settings Job Failure Notification Raise event if job fails unexpectedly? Event severity when job fails unexpectedly Select Yes to raise an event if the AMHealth_CCComponentsHealth job fails unexpectedly. The default is Yes. an event that is raised when the job fails unexpectedly. The default is 5. Additional Settings Event Details Event detail format Select the format in which you want to display the event detail. You can select from HTML Table or Plain Text. The default is HTML Table. Event Notification AM Health Knowledge Scripts 23

24 Parameter Raise an event if SQL Server services are down? (Use MC based Action Script for notification) Event severity when SQL Server services are down Restart SQL Server services that stop unexpectedly? Select Yes to raise an event if Control Center SQL Server services are down. The default is Yes. Tip Use Action Script for notification, as the Control Center repository will not be available. an event in which SQL Server services are down. The default is 10. Select Yes to restart SQL Server services that stop unexpectedly, such as when not as part of scheduled maintenance. The default is Yes. Raise an event if SQL Server services cannot be restarted? Select Yes to raise an event if SQL Server services cannot be restarted. The default is Yes. Tip Use Action Script for notification, as the Control Center repository will not be available. Event severity when SQL Server services cannot be restarted Raise an event if SQL Server services are restarted? Event severity when SQL Server services are restarted Raise an event if Control Center Cache Manager errors occur? Set the event severity, from 1 to 40, to indicate the importance of an event in which SQL Server services cannot be restarted. The default is 5. Select Yes to raise an event if SQL Server services are successfully restarted. The default is Yes. an event in which SQL Server services are successfully restarted. The default is 25. Select Yes to raise an event if the Control Center Cache Manager experiences one of the following: An error related to Microsoft Distributed Transaction Control (MSDTC). An error with the synchronization of data between Control Center and the QDB repositories that are synchronized to Control Center. An error from a Control Center SQL Server agent job that has failed. The default is Yes. NOTE: Not all Control Center SQL jobs are monitored. Only those that are related to Cache Manager are monitored. The following jobs are monitored for errors that affect Cache Manager: NetIQ CC Manage SQL Jobs NQCCDB NetIQ CC Hourly Task NQCCDB NetIQ CC Half-Hourly Task NQCCDB NetIQ CC Daily Task NQCCDB Cache Manager is a child process of the CQS. Cache Manager runs the Control Center queries on AppManager repository computers to retrieve view information for Control Center s. After the first iteration of the Knowledge Script completes, only new errors generated since the previous iteration will be raised as events. Event severity when Cache Manager errors occur Set the event severity, from 1 to 40, to indicate the importance of an event in which Cache Manager experiences errors. The default is NetIQ AppManager for Self Monitoring (AM Health) Management Guide

25 Parameter Raise an event if Control Center SQL jobs are missing? Select Yes to raise an event if SQL jobs are missing. The default is Yes. A missing job is one that might have been deleted or renamed. Event severity when Control Center SQL jobs are missing Raise an event if Control Center SQL jobs are disabled? Event severity when Control Center SQL jobs are disabled Enable Control Center SQL jobs that are disabled? Event severity when SQL jobs cannot be enabled Raise an event if Control Center SQL jobs are successfully enabled? Event severity when Control Center SQL jobs are successfully enabled Raise an event if a Control Center SQL Server job fails? Event severity when a Control Center SQL Server job fails Raise an event if Control Center server disks are fragmented? Set the event severity, from 1 to 40, to indicate the importance of an event in which SQL jobs are missing. The default is 15. Select Yes to raise an event if SQL jobs are disabled. The default is Yes. Set the event severity, from 1 to 40, to indicate the importance of an event in which SQL jobs are disabled. The default is 15. Select Yes to enable, or start, SQL jobs that are disabled. The default is No. Set the event severity, from 1 to 40, to indicate the importance of an event in which disabled SQL jobs cannot be enabled, or started. The default is 20. Select Yes to raise an event if disabled SQL jobs are successfully enabled, or started. The default is No. an event in which disabled SQL jobs are successfully enabled, or started. The default is 20. Select Yes to raise an event if any step in a SQL Server job fails. The default is Yes. an event in which a SQL Server job fails. The default is 20. Select Yes to raise an event if disks on the Control Center server are fragmented. The default is Yes. Tip To avoid errors when running this script on a Windows Server 2008 server, disable User Account Control (UAC). Event severity when Control Center server disks are fragmented Raise an event if Control Center database size exceeds threshold? Threshold - Maximum Control Center database size Event severity when Control Center database size exceeds threshold Raise an event if query process time exceeds threshold? an event in which disk fragmentation has occurred on the Control Center server. The default is 15. Select Yes to raise an event if the Control Center database size exceeds the threshold you set. The default is Yes. NOTE: This parameter is applicable only on AppManager 9.1 running on SQL Server Express edition. Specify how large the Control Center database file can grow before raising an event. If the database file size is too small, AppManager performance will not be optimal in larger environments. The default is 8 GBytes. an event in which the Control Center database file size exceeds the threshold. The default is 20. Select Yes to raise an event if the amount of time it takes to process a SQL query exceeds the threshold you set. The default is Yes. AM Health Knowledge Scripts 25

26 Parameter Threshold -- Maximum process run time Specify the maximum length of time it can take SQL Server processes to run before an event is raised. The default is 300 seconds. Event severity when query process time exceeds threshold an event in which SQL query processing time exceeds the threshold you set. The default is 10. Event severity when query process time cannot be retrieved an event in which the script cannot determine the processing time for SQL queries. Processing time could be prevented from being retrieved if the query fails due to blocking, or if a connection cannot be made to the Control Center QDB SQL Server, which would cause the query to fail. If the query fails, the event will be raised without exception, which would inform users if there was an issue with the Control Center QDB SQL Server. The default is 10. Raise an event if Deployment services are down? Select Yes to raise an event if Control Center deployment services are down. The default is Yes. The following situations can cause deployment services to be down: The Control Center server is restarted. Deployment services took too long to restart. The connection to the Control Center repository is unavailable. The proxy server is unavailable. Event severity when Deployment services are down Raise an event if unable to retrieve Control Center component information? Event severity when unable to retrieve Control Center component information an event in which deployment services are down. The default is 10. Select Yes to raise an event if the script does not have the discovery details for the Control Center components, or if the discovery details are empty. The default is Yes. an event in which AppManager cannot retrieve Control Center Component information. The default is 10. NetIQ Control Center Command Queue Service Monitoring Raise an event if Command Queue Service is not connected to the Control Center database? Event severity when Command Queue Service is not connected to the Control Center database Raise an event if Command Queue Service is down? Event severity when Command Queue Service is down Select Yes to raise an event if the Command Queue Service (CQS) is not connected to the Control Center database (NQCCDB). The default is Yes. The CQS polls the Command Queue table for queries to run. The Command Queue table stores queries that collect view information based on the criteria defined in Control Center. Set the event severity, from 1 to 40, to indicate the importance of an event in which the CQS is not connected to the Control Center database (NQCCDB). The default is 10. Select Yes to raise an event if the CQS is down. The default is Yes. an event in which CQS is down. The default is NetIQ AppManager for Self Monitoring (AM Health) Management Guide

27 Parameter Restart Command Queue Service if the service is down? Raise an event if Command Queue Service is restarted? Event severity when Command Queue Service is restarted Raise an event if Command Queue Service cannot be restarted? Event severity when Command Queue Service cannot be restarted Select Yes to restart CQS if it is down. The default is Yes. Select Yes to raise an event if CQS is successfully restarted. The default is Yes. an event in which CQS is successfully restarted. The default is 25. Select Yes to raise an event if CQS cannot be restarted. The default is Yes. an event in which CQS cannot be restarted. The default is 5. SQL Server File Size and Growth Settings Monitoring Raise an event if insufficient space available for further file growth? Select Yes to raise an event if the amount of available disk space is not enough to allow the file to continue to grow. SQL Server has growth settings on the Database Data and Log files. If the amount of free space on the disk is lower than this growth setting, an event will be raised to keep the files from attempting to grow and causing the SQL Server databases to become corrupted. The default is Yes. Event severity when available space is insufficient Raise an event if file growth rate falls below the threshold? an event in which the available server space is insufficient. The default is 10. Select Yes to raise an event if the growth rate of the database data and log files falls below the threshold you set. If the growth rate is low, the data and log files become fragmented, which negatively impacts performance. NOTE: The two threshold parameters (MB and percentage) are evaluated individually depending on whether the database file growth setting is in MB or a percentage. The default is Yes. Threshold -- Minimum growth rate in MB Threshold -- Minimum growth rate in percentage Event severity when file growth rate falls below the threshold Raise an event if Autogrowth is not enabled and file usage exceeds the threshold? Specify in megabytes the minimum growth rate of SQL Server files before an event is raised. The default is 256 MB. Specify as a percentage the minimum growth rate of SQL Server files before an event is raised. The default is 9%. an event in which the rate of growth of SQL Server files falls below the threshold you set. The default is 10. Select Yes to raise an event if the file usage exceeds the threshold and Autogrowth is not enabled. The default is Yes. The Autogrowth feature allows a database to grow by the amount of space required by a file or a transaction. Threshold -- Maximum file usage with Autogrowth disabled Specify the maximum amount of file usage with Autogrowth disabled that can occur before an event is raised. The default is 90%. AM Health Knowledge Scripts 27

28 Parameter Event severity when Autogrowth disabled and usage exceeds threshold Raise an event if SQL Server maximum file size exceeds available disk space? Event severity when SQL maximum file size exceeds disk space an event in which the file usage exceeds the threshold and Autogrowth is not enabled. The default is 10. Select Yes to raise an event if the maximum SQL file size (MAXSIZE) is set to a value greater than the amount of available disk space. The default is No. The MAXSIZE value identifies the maximum size to which a SQL Server database can grow. an event in which the maximum SQL file size is set to a value greater than the amount of available disk space. The default is 15. Data Collection Collect data for database space utilization? Collect data for log space utilization? Collect data for Command Queue Server connection status? Collect data for SQL Server service status? Select Yes to collect data for charts and reports. If enabled, data collection returns the percentage of database space used on the Control Center server. The default is No. Select Yes to collect data for charts and reports. If enabled, data collection returns the percentage of log space used on the Control Center server. The default is No. Select Yes to collect data for charts and reports. If enabled, data collection returns 100 if CQS is up and 0 if CQS is down. The default is No. NOTE: This script only collects data for the CQS connection status when you run the script on the Control Center database (NQCCDB). The script does not collect data when you run it on the CQS. Select Yes to collect data for charts and reports. If enabled, data collection returns 100 if SQL Server services are up and 0 if SQL Server services are down. The default is No. Monitoring SQL username Specify the username required to access SQL Server on the Control Center server. Ensure that the user has sufficient permission to access SQL Server on the Control Center server. For more information, see the Configuring Security Manager for AM Health section in AppManager for Self Monitoring Management Guide. 3.3 HeartbeatUNIX Use this Knowledge Script to monitor the heartbeat of the AppManager agent running on a UNIX or Linux server. A heartbeat is a periodic signal generated by an AppManager agent computer to indicate that it is still running. If an AppManager agent fails to send either data or an event to the QDB within the specified grace period, this script considers the agent to be offline. This Knowledge Script also monitors the health of jobs running on UNIX and Linux agents. Use this script to monitor Knowledge Script job run time against job schedule and against a user-specified maximum run time. NOTE: Job monitoring is only available for UNIX agent 8.0 and above. 28 NetIQ AppManager for Self Monitoring (AM Health) Management Guide