|
 Monitoring Studio Express is a Performance Manager specifically designed for BMC Portal; consequently, it uses the same common features and procedures of BMC® Portal. Please refer to your BMC Portal guides for basic knowledge on how to use the Portal. This document assumes that the user knows how to use the Portal and therefore explains procedures only related to BMC Performance Manager Express Monitoring Studio, and not on how to add Elements, Element Profiles etc…
To create an instance of the LOG File Monitoring and Analysis tool
| 1. | Go to the Configure tab, click on the element on which you wish to use the tool. |
 If the element was created using Element Profile then add the new application class through the same route.
| 2. | On the Element Properties page, scroll to the Application Class section, click on Add. |
| 3. | On the Add Applications page, select Miscellaneous from the drop down category list and click Next. |
All application classes belonging to the BMC Performance Manager Express Monitoring Studio package are listed under Miscellaneous.
| 4. | On the Available Application Classes page, select Studio - LOG File Analysis and select the number of LOG file analysis instances you wish to create, click Next. You can create up to 10 instances at this stage, or create just 1 now and add others later. |
| 5. | You arrive at the Properties and Credentials page. Enter the information required for setting up the LOG File Analysis instance and click Add. |
The "Information Required for Monitoring" at this step differs depending whether the LOG file is monitored on a Windows system or a UNIX/Linux system. The rest of the procedure and interface is the same irrespective of the type of system.
Information required for monitoring
|
|
|
|
Descriptive Label
|
Label describing the application class/monitoring tool
|
Collection Interval
|
Frequency of collection (monitoring/polling). Unit: Minutes (Default 5 minutes)
|
Credentials
Connect As
Password
Credentials
Access As
Password
Credentials
|
Login used to connect to the remote element through WMI
Password associated with the login above
Shared credentials used for authentication
N/A
|
Login used to connect to the remote element through Telnet or SSH
Password associated with the login above
Shared credentials used for authentication
Login used to access the file. Specify only if you need to use a different login than the "Connect As" login specified above. Once connected, the "su" command will be used to impersonate as the specified user and access the file.
Password associated with the login above
Shared credentials used for authentication
|
Hostname
|
Hostname or IP address of the remote element (Appears by default)
|
Remote Access Method
|
N/A (Automatically connects using WMI)
|
Telnet or SSH. Select the method to connect to the remote element.
|
Debug Mode
|
"Yes" enables the debug mode, while "No" disables it. The debug output produced is stored on the RSM server in a file located at:
%RSM_HOME%/RSM(xx)/SEN_MS/sen_ms_debug_file_hostname.log.
Do not leave the debug mode enabled for too long as the debug file may grow indefinitely.
|
| 6. | Enter the information and click Next and you arrive at the Properties and Credentials page asking for the Input properties of the new LOG file instance. Enter the required input to create the instance: |
Input Properties
|
|
|
Descriptive Label
|
Enter a label to describe this new LOG file monitoring instance.
|
LOG File Path
|
Specify the LOG file name with its complete path, or, enter just the path to the directory containing the file. If the directory is indicated, it is the most recently modified LOG file that is considered.
Note: You can use wild characters (‘*’ and ‘?’) in the file path.
|
Perform Parsing
|
Select an option from the drop-down list.
Parsing on the managed element could result in higher CPU usage but lower network traffic, this depends on the file size/file growth.
Parsing on the RSM results in lower CPU usage but could cause higher network traffic, this It depends on the file size/file growth.
|
| 7. | Either click Next to arrive at the thresholds setting page, or, add a string search or a numeric value extraction for this LOG file instance. The string search and numeric value extraction instances can also be set later on this instance. |
| 8. | On clicking Next the input properties are displayed grayed-out. This page allows you to verify, edit or delete the newly-created instances and/or add another instance for the same element. If the information is correct, go on to the next step. |
| 9. | You are at the Thresholds, Properties and Credentials page. Set thresholds and alert conditions: By default, the Exists parameter is enabled to raise an Alarm if the file is not present. You can modify this setting if it does not suit your requirements. |
| 10. | Thresholds and alerts can be set for each parameter. Check the Warning and/or Alarm boxes next to the parameters to activate alerts as per your specific requirements. See details of parameters and alert conditions in the Reference Guide. |
Thresholds can be set or modified at any time by clicking on the element > Configure > ”application class name” > Edit Thresholds, Properties and Credentials.
| 11. | Click Finish. Changes have been Saved message pops up, and an icon appears in the left pane of the window displaying the newly-created LOG file instance. Under Application classes the new class appears bearing the label as set by the user. |
You have successfully setup a LOG File Monitoring and Analysis instance.
Editing or Deleting an instance
To edit or delete the instance, follow the regular procedure as for all Performance Managers on the Portal, or see Editing or Deleting an Instance.
|
