Enabling application diagnostic event monitoring in BMC ProactiveNet
Integration with BMC ProactiveNet enables you to combine proactively detected performance issues with deep application diagnostics. Perform the following procedure to configure the BMC Application Management Console to send events to BMC ProactiveNet.
BMC ProactiveNet Cells are event-processing engines that store all events and data in memory and on disk. If the BMC ProactiveNet Cell is in high-availability mode, enter the secondary BMC ProactiveNet Cell information.
To perform this procedure, you must have Administrator-level access, or higher.
To set up integration in the Console
- In the BMC Application Management Console, from the Diagnostics tab, click Administration > Integration Configuration.
- Configure the Console for integrations.
- In the Console, click System Deployment, and then click ProactiveNet integration.
- In the Action menu, select Edit BMC ProactiveNet Integration.
Enter the BMC ProactiveNet connection details.
The following table describes the options for the BMC ProactiveNet integration configuration:
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
1. If the BMC ProactiveNet Cell is in high-availability mode, enter the secondary BMC ProactiveNet Cell information. Otherwise, leave these fields blank.- (Optional) To test the connection credentials, click Test Credentials.
- Click Save.
- Click the switch to activate or deactivate the feature:
- Activated switch
- Deactivated switch
- Activated switch
To set up the BMC Application Diagnostics event rule in BMC ProactiveNet
If you are integrating with a version of BMC ProactiveNet that is earlier than version 9.5, perform the following procedure to enable BMC Application Diagnostics to close events in BMC ProactiveNet. You must add the event rule to the BMC ProactiveNet Cell, compile, and then restart the cell.
Download the app_diagnostics_close_event.mrl event rule from the Electronic Product Distribution (EPD), under the BMC Application Diagnostics node.
You can find the file in one of the following locations:- In the downloaded BMC Application Diagnostics Server ZIP file:
- (Windows) \files\bppm
- (Linux) /files/bppm
- In the installation directory:
- (Windows) installationDirectory\BMC_Application_Diagnostics\portal\resources\bppm
- (Linux) installationDirectory/BMC_Application_Diagnostics/portal/resources/bppm
- In the downloaded BMC Application Diagnostics Server ZIP file:
- Copy the event rule to the BMC ProactiveNet computer to the %MCELL_HOME%/etc/<cellName>/kb/rules directory.
The <cellName> variable represents the name of the primary BMC ProactiveNet Cell that receives BMC Application Diagnostics events. - In the %MCELL_HOME%/etc/<cellName>/kb/rules directory, open the .load file with a text editor and add the rule name, app_diagnostics_close_event, to the list.
- Navigate to the cell folder, for example, C:\Program Files\BMC Software\ProactiveNet\pw\server\etc\pncell_CellServerName.
To compile the cell with the added rule, run the following command-line interface (CLI) command:
mccomp –n <cellName>
To stop the cell, run the following command:
mkill –n <cellName>
To start the cell, run the following command:
mcell –n <cellName>
- If the BMC ProactiveNet Cell is in high-availability mode, repeat the procedure for the secondary cell.
In addition to seeing diagnostics data in the event views of BMC ProactiveNet, BMC Application Diagnostics integration can show events in defined services. You can include the Agent and monitored services in a service model, and in this way, gain a better understanding of the impact of the event on your monitored service. For information about BMC ProactiveNet, see BMC ProactiveNet online technical documentation.