Monitoring Applications with Monitoring Studio X

1. Monitoring Applications with Monitoring Studio X

2. Course Overview

3. Objectives At the end of this course, you should be able to:

4. Getting Started About Monitoring Studio X Top Features Basic Concepts Monitors Available

5. 100 % Monitored with pre-built modules Monitored with Monitoring Studio A Configurable Module to Fill Monitoring Gaps TrueSight Operations Management Pre-built Knowledge Modules for: Servers: Windows, UNIX, Linux Virtual Servers: VMware, Citrix, Amazon Web Services, etc. Databases, Middleware: Oracle, Sybase, WebSphere, JBoss, etc. Standard Applications: Exchange, SAP, etc. Monitoring Studio X A configurable module to cover the rest (REST, CLI, WMI, SSH, SQL, SNMP, etc.) Application Middleware Operating system Hardware

6. The 5 Top Features of Monitoring Studio X Modern Web UI Live Interactions Unified Configuration Monitoring Capabilities Mass Deployment Configure the monitoring of business applications and PATROL Agent settings in one place. Monitoring Studio X still offers all the powerful monitoring capabilities of previous versions. Monitoring templates deployment in TrueSight limited to 3 simple steps. Developed with the most popular front-end and back-end technologies. Interact in real-time with the PATROL Agent and its main components through a REST API.

7. General Concepts Hosts: Provide information about the target server where the technology to be monitored is running. They are created independently and can use none, one, or several templates Templates: Technology to be monitored. Attached to one or several hosts, templates contain the list of monitors and additional credentials Monitors: Define a monitoring action in a Template. Monitors are therefore directly attached to Templates in the configuration. Credentials: Credentials are declared at the Template level and set at the Host level.

8. Monitors Available 3 types of Monitors Basic Monitors (File System, Process, Windows Events, etc.) Monitors with Content (Command Line, File, Folder, HTTP Request, etc.) Parsing Content Monitors (String Search, Numeric Value Extraction, Value Map, Dynamic Objects)

9. Setting up Monitoring Studio X Configuring Monitoring Studio X to monitor applications

10. Setting up Monitoring Studio X Install Monitoring Studio X and the PATROL Agent on a TEST system Configure your monitoring template on the TEST environment Export the template and import it into a CMA policy in TrueSight Deploy Monitoring Studio X and the policy to the relevant production systems

11. Installing Monitoring Studio X Install Monitoring Studio X on your PATROL agents just like any standard KM either through : • the BMC Installation Utility • or BMC TrueSight Enter this URL in your Web browser to access the Web Interface :https://<patrol-agent>:<patrol-agent-port+262>/

12. Configuring Your Monitoring Templates

13. General Procedure

14. Defining Hosts Info required by Monitoring Studio X: System Type (Windows, UNIX/Linux, or Other) List of Hostnames or IP addresses of the hosts to be monitored Optional Settings: System Credentials SNMP settings Availability check

15. Creating Monitoring Templates Option 1: Import in Monitoring Studio X the free Templates available on Option 2: Create your own Template and provide the required information : Host system type to which the template will apply The required credentials The Monitors to be used.

16. Applying Templates to Hosts Templates are applied at the Host level. The Templates available for hosts depend on both the host type and the template type: Templates for All Systems apply to any host type Templates for Windows Systems apply to Windows hosts only Templates for Linux/UNIX apply to Linux/UNIX hosts only.

17. ConfiguringBasic Monitors File System, Process, SNMP Trap, Windows Events, Windows Performance Counters, and Windows Service

18. File System Monitor Purpose: Monitor a file system critical for the monitored system/ application Info required by Monitoring Studio X: The file system path Parameters: Available capacity, percentage of available Inodes, consumed capacity growth Typical use case: Be informed when the disk space available is low

19. Process Monitor Purpose: Monitor one or several processes Info required by Monitoring Studio X: The process name, its command line, or its user ID. Parameters: Number of matching processes, total processor time utilization, total memory consumption, etc. Typical use case: Ensure that the monitored application is functioning properly by checking that processes are running. If they are not, restart them using Alert Actions.

20. SNMP Trap Monitor Purpose: Listen for SNMP traps and enable rapid recovery actions depending on the traps received Requirement: Enable the SNMP Agent to send the traps to the PATROL Agent where Monitoring Studio X is installed Info required by Monitoring Studio X: Enterprise OID, Varbind OIDs and values Parameters: Matching trap count, matching trap rate Typical use case: Be informed when an SNMP trap is sent and trigger recovery actions.

21. Windows Event Monitor Purpose: Monitor events posted to the Windows Event Log. Info required by Monitoring Studio X: The Windows Event Log to be monitored, the Event Source (provider name) and when alerts should be triggered Parameters: Number of matching events and rate at which they are found Typical use case: Track events posted to the Windows Event Log and generate an alert when a specific event is found.

22. Windows Performance Counter Monitor Purpose: Monitor Windows Performance Counters. Info required by Monitoring Studio X: Name of the Windows performance object that contains the counter to be monitored Name of the instance to be monitored. Parameters: Value of the Windows Performance Counter. Typical use case: Monitor Windows Performance Counters to know how applications affect the server’s performance.

23. Windows Service Monitor Purpose: Monitor the state of a Windows service and interpret the state to determine its status Requirement: Both the PATROL Agent and the monitored host must be running on Windows Info required by Monitoring Studio X: Short name of the Windows service Parameters: Service details and status Typical use case: Monitor Windows services and generate an alert when their status is Suspicious or Failed.

24. ConfiguringMonitors with Content Monitors that generate content that can later be analyzed by Content Parsing Monitors

25. Command Line Monitor Purpose: Run commands or in-house scripts and analyze their result on a regular basic. Info required by Monitoring Studio X: Command line (shell command, shell script, or executable file with arguments) to be executed Credentials required to run the command Parameters: Execution time, exit code, result, and status. The result can later be analyzed with Content Parsing Monitors.

26. Database Query (SQL) Monitor Purpose: Execute an SQL statement against a database server to: check the availability of the database check the result of a specific query extract data of interest for monitoring Info required by Monitoring Studio X: The type of database (set at the Template level) The SQL query to run The database-specific information (set in the Host page when applying the Template) Parameters: Execution time, result, and status. The result can later be analyzed with Content Parsing Monitors.

27. File Monitor Purpose: Check the presence of a log or flat file, monitor its size, growth percentage and speed. Know when it was last modified. Parse its content. Info required by Monitoring Studio X: File path Parameters: Presence, growth percentage and speed, size, elapsed time since file was last modified. The result can later be analyzed with Content Parsing Monitors.

28. Folder Monitor Purpose: Monitor the directories used by your applications to ensure that the application is not overloaded and measure the applications activity. Info required by Monitoring Studio X: Folder path. Parameters: Presence, folder size, number of files, growth percentage and speed, several rates, etc. The result can later be analyzed with Content Parsing Monitors.

29. HTTP Request Monitor Purpose: Perform an HTTP request and analyze the response of the HTTP server to: monitor the availability of a Web page, extract useful information from a Web-based administration user interface, extract data from a Web service, extract data from a REST API. Info required by Monitoring Studio X: The URL containing the hostname of the HTTP server. (Optional] Authentication method to be used, HTTP request headers and body, and HTTP status codes. Parameters: Status, execution time, and HTTP status code The result can later be analyzed with Content Parsing Monitors.

30. Nagios Plugin Monitor Purpose: Execute any Nagios plugin and monitor the results in TrueSight without requiring a native Nagios environment. Info required by Monitoring Studio X: Command to run the Nagios plugin. Parameters: Execution time and status. The result can later be analyzed with Content Parsing Monitors.

31. Parameter Combination Monitor Purpose: Combine any Monitor parameter of the Template with a mathematical formula or a PSL statement. Info required by Monitoring Studio X: Variables to be processed and the formula to apply. Predefined PSL functions are supported. Parameters: Result and value. The result can later be analyzed with Content Parsing Monitors.

32. PSL Script Monitor Purpose: Run PSL commands on the local PATROL Agent system to check the PATROL Agent health. Info required by Monitoring Studio X: PSL command or script to be executed. Parameters: Execution time, result, and status. The result can later be analyzed with Content Parsing Monitors.

33. SNMP Polling Monitor Purpose: Poll the SNMP agent and retrieve the value of a given OID or the values of an SNMP table. Info required by Monitoring Studio X: Info required will vary whether Monitoring Studio X polls a single OID or an SNMP table. Parameters: Execution time, result, status, and value. The result can later be analyzed with Content Parsing Monitors.

34. WBEM Query Monitor Purpose: Query a WBEM provider. Info required by Monitoring Studio X: The WBEM namespace and a WQL query. Parameters: Execution time, result, and status. The result can later be analyzed with Content Parsing Monitors.

35. WMI Query Monitor (For Windows Hosts Only) Purpose: Execute a WQL query against a Windows host and analyze its result. Info required by Monitoring Studio X: WMI query to be run and WMI namespace. Parameters: Execution time, result, and status. The result can later be analyzed with Content Parsing Monitors.

36. Configuring Content Parsing Monitors Monitors to parse the content generated by the Monitors with Content

37. Text Pre-Processing Monitor Purpose: Transform a multi-line, XML, JSON, or HTML content into a simpler format (single line, CSV, flat map, etc.) to be parsed by the Content Parsing Monitors. Info required by Monitoring Studio X: Transformation to be applied. Parameter: Result.

38. String Search Monitor Purpose: Search for a specific string in the information sources previously configured (flat or log files, output of a Web request or a database query, OID content, etc.) Info required by Monitoring Studio X: String(s) to be searched, where the string(s) should be found, and how alerts should be acknowledged Parameters: Last matching lines, matching line count, and matching line rate. Typical usage: Search for the Failure or Error string in a log file to be informed as soon as a problem occurs and to have Monitoring Studio X acknowledge the alert when the Success string is found.

39. Numeric Value Extraction Monitor Purpose: Extract a number from the information sources previously configured. Info required by Monitoring Studio X: Information source, location and position of the numeric value in the searched lines, and the value to be considered. Parameters: Presence and value.

40. Value Map Monitor Purpose: Extract values from result outputs generated by other Monitors and map up to 25 of these values to user-defined statuses. Info required by Monitoring Studio X: The source from which the values will be extracted, where the values can be found and how to map them. Parameters: Status and status information.

41. Dynamic Object Monitor Purpose: Dynamically create Monitor objects based on the Result generated by a parentMonitor with Content and create an instance for each line found in the Result parameter. Info required by Monitoring Studio X: Instance ID, object name, column separator. Parameters: Presence and result. Only available for the File, Command Line, HTTP Request, WMI Query, WBEM Query, Database Query, SNMP Polling, PSL Script, and Nagios Plugin Monitor Pages.

42. Configuring Alerts Alerts and Alert Messages

43. Configuring Alerts Purpose: Configure any numeric parameter to trigger alerts, send notifications and take specific actions when certain conditions are met. Possible alarms: Alarm #1 and #2 to define the range of values that trigger warnings and alarms. Out-of-range to be informed when values are outside the norm.

44. Configuring Alert Messages Purpose: Define how you will be notified when alert conditions are detected. Possible Alert Messages: Annotation PATROL Event Command Line PSL Script Email Write to a Log File Send an SNMP Trap Default message content can be customized with macros.

45. Deploying in TrueSight

46. Deploying in TrueSight Monitoring Studio X Web Interface TrueSight - CMA

47. Additional Features

48. Embedded Files Purpose: Helps ensure that files are distributed along with the Template configuration. Embedded files are: text files saved in the Template configuration itself. referred to from the Command Line or Nagios Plugin Monitors with the %{FILE:<filename>} macro

49. The Dry Run Feature Purpose: Challenge your monitoring settings before implementing them by conducting dry runs (live testing) Available for all Monitors with Content Procedure: Configure a Monitor with Content Select the Host on which the technology to be monitored is installed Click the Dry Run button. Check the preview on the right pane. If problems are detected, make the needed adjustments.

50. The PATROL REST API Purpose: Interact with the PATROL Agent and its main components: authentication agent, platform info, troubleshooting (get) agent configuration (get, set, download) namespace (get) events (get) console (get, history) studio (get, set, download) All functions are fully documented: https://www.sentrysoftware.com/library/swagger-ui/?url=/openapi.yaml