Configuring and activating integrated technologies

You can configure integrations for supported products and technologies. With integrated products and technologies, you can view events and event notifications from BMC Application Diagnostics.

You can send the following kinds of events:

  • Application events, such as crossing a latency threshold and percentage of errors
  • Application server events, such as JMX metrics, thread pools, and connection pools
  • System health events, such as issues with BMC Application Diagnostics Agents, Collectors or the Portal

Except where noted, events that are sent to the integrated product or technology contain a hyperlink to the Application View in BMC Application Diagnostics.

The following topics are presented:

Before you begin

Before you configure and activate integrated technologies, ensure that you review the following topics:

Configuring the BMC Application Performance Management Console for integrations

For any integrated technology, configure the BMC Application Performance Management Console for integrations. The following procedure defines the properties of the Console address so that integrated products can link to BMC Application Diagnostics.

To perform this procedure, you must have Administrator-level access, or higher.

  1. In the BMC Application Performance Management Console, from the Diagnostics tab, click Administration > Integration Configuration.
  2. In the BMC APM Console Address panel, click the arrow in the upper-right corner and select Edit.
  3. Enter the Console details:
    • Host Name / IP Address: Host name or IP address of the Console computer
    • Port: Listening port on the Console computer. The default value is 443.
  4. Click Save.

Integrating with 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 Diagnostics Server 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 BMC Application Management Console

Click to expand steps.
  1. Configure the BMC Application Performance Management Console for integrations.
  2. In the BMC ProactiveNet Integration panel, click the arrow in the upper-right corner and select Edit.

  3. 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.

  4. Click Save.

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. (BMC ProactiveNet 9.5, or later, includes the BMC Application Diagnostics event rule out of the box.)

Click to expand steps.
  1. Locate the app_diagnostics_close_event.mrlevent rule that was downloaded with the Server files in one of the following locations:
    • In the downloaded BMC Application Diagnostics Server ZIP file:
      • (Windows) ADOPServer\Disk1\files\bppm
      • (Linux) ADOPServer/Disk1/files/bppm
    • In the installation directory:
      • (Windows) installationDirectory\BMC_Application_Diagnostics\portal\resources\bppm
      • (Linux) installationDirectory/BMC_Application_Diagnostics/portal/resources/bppm
  2. 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.
  3. 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.

  4. To compile the cell with the added rule, run the following command-line interface (CLI) command:

    mccomp –n <cellName>

  5. To stop the cell, run the following CLI command:

    mkill –n <cellName>

  6. To start the cell, run the following CLI command:

    mcell –n <cellName>

  7. 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.

Configuring monitoring over SNMP

Perform the following procedure to configure the BMC Application Diagnostics Server to send events using Simple Network Management Protocol (SNMP).

To perform this procedure, you must have Administrator-level access, or higher, or have tenant Application Owner-level access.

  1. Configure the BMC Application Performance Management Console for integrations.
  2. In the SNMP Integration panel, click the arrow in the upper-right corner and select Edit.

  3. Enter the SNMP connection details.

    The following table describes the options for the SNMP integration configuration:

     

  4. Click Save.

Configuring notification with SMTP

Perform the following procedure to configure the BMC Application Diagnostics Server to send email notification of events using Simple Mail Transfer Protocol (SMTP).

To perform this procedure, you must have Administrator-level access, or higher, or have tenant Application Owner-level access.

  1. Configure the BMC Application Performance Management Console for integrations.
  2. In the SMTP Integration panel, click the arrow in the upper-right corner and select Edit.

  3. Enter the SMTP connection details.

    The following table describes the options for the SMTP integration configuration:

     

  4. Click Save.

Configuring Syslog integration

Perform the following procedure to configure the BMC Application Diagnostics Server to send events to syslog.

To perform this procedure, you must have Administrator-level access, or higher, or have tenant Application Owner-level access.

  1. Configure the BMC Application Performance Management Console for integrations.
  2. In the Syslog Integration panel, click the arrow in the upper-right corner and select Edit.

  3. Enter the Syslog connection details.

    The following table describes the options for the Syslog integration configuration: 

  4. Click Save.

Writing events to a CSV file

By default, the server writes to a comma-separated values (CSV) file, events.csv, located on the BMC Application Diagnostics Portal computer, in the <installationDirectory>\portal\logs\events directory. Events in the CSV file do not contain hyperlinks to BMC Application Diagnostics.

To perform this procedure, you must have Administrator-level access, or higher.

  1. Configure the BMC Application Performance Management Console for integrations.
  2. In the CSV Event Logging panel, click the switch to disable or enable the BMC Application Diagnostics Server to write events to the CSV file.

Activating and deactivating integrations

After you configure an integration, you can click the switch to activate or deactivate the feature.

To perform this procedure, you must have Administrator-level access, or higher, or have tenant Application Owner-level access.

  • Activated switch apm_console_switch_enabled.png
  • Deactivated switch apm_console_switch_disabled.png

Configuring BMC Application Diagnostics integration with BMC Real End User Experience Monitoring

If you integrate between the BMC Application Diagnostics product and the BMC Real End User Experience Monitoring product, you can navigate between the products to view session details and application health.

For on-premises or service-provider users with Administrator-level access, or higher, see integration details at Integrating-with-BMC-Real-End-User-Experience-Monitoring.

For tenant users with tenant Application Owner-level access, perform the following procedure to select the component to be integrated with BMC Application Diagnostics: either the Session Overview page of the Performance Analysis, or the Session Browser page of a Real User Analyzer instance:

  1. In the BMC Application Performance Management Console, click Diagnostics and select Administration > Integration Configuration.
  2. In the BMC Real End User Experience Monitoring Integration panel, from the shortcut menu, select Edit.
  3. Select the type of the integration and click Save:
    • No Integration. Select this option to remove integration between the products.
    • Session Overview (Performance Analysis). BMC Application Diagnostics is integrated with the Session Overview plug-in.
    • Session Browser (Real User Analyzer). BMC Application Diagnostics is integrated with the Real User Analyzer feature.

Integrating with external monitoring applications

If you use an external monitoring application, then BMC Application Diagnostics can provide a detailed view of specially tagged transactions. Transactions with matching tags are persisted, regardless of sampling or thresholds configuration.

For configuration details, see Configuring-persistence-of-tagged-transactions.

Related topic

Application-server-events-reference
Working-with-logs

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*