Integrating with BMC Real End User Experience Monitoring

Tip

For more information about the BMC Real End User Experience Monitoring licensed product,see BMC Real End User Experience Monitoring online technical documentation.

BMC Application Diagnostics is a licensed add-in for the BMC Application Management Suite.

Integrating BMC Real End User Experience Monitoring with BMC Application Diagnostics enables you to perform the following actions:

  • Access diagnostics data for a specific transaction in a BMC Real End User Experience Monitoring session.
  • Access session data from specific trace details that are captured in BMC Application Diagnostics.

This topic presents the following sections:

The following video (5:43) describes the benefits of the integration, and how to set it up.

Use player to increase quality or switch to full screen | YouTube www.youtube.com/watch?v=A0rgU4vfdAk

Before you begin

Install BMC Real End User Experience Monitoring components. For information about installing the product, see Installation-process-overview in the BMC Real End User Experience Monitoring documentation.

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

To set up integration in the BMC Application Management Console

  1. In the BMC Application Management Console, define the properties of the Console address so that BMC Real End User Experience Monitoring can link to BMC Application Diagnostics:

    1. Open the Diagnostics > Administration > Integration Configuration page and edit the BMC APM Console Address field.
    2. Provide host name (or IP address) and port of the Console and click Save.

     

  2. 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. Open the Diagnostics > Administration > Integration Configuration page.
    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:
      • 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.
        BMC Application Diagnostics on-premises users, or a service-provider user who needs system configuration, must enter the host name or IP address for the Real User Analyzer.
        If you are using the Session Browser, continue to the following procedure, "To set up the integration in the Real User Analyzer."

To set up the integration in the Real User Analyzer

If the BMC Application Diagnostics integration is through the Session Browser, perform the following procedure to configure the Application Visibility Servers in the Real User Analyzer.

Click to expand steps.
  1. In the Real User Analyzer, open the Administration > Integration > Application Visibility Servers  page and add new application visibility server so the system will be able to connect to your portal:

    1. Set the URL of an application visibility server and click Save.
      For example:

      http://<Portal_IP>:<Portal_Port>/portal/rest/truesight
    2. Based on the visibility server's authentication, select the authentication method — Basic or Form-based. If no authentication is necessary, select None.

    3. Provide access credentials (if the authentication method is not selected, skip this step).
      The application visibility server is added to the system.

      Application visibility servers page

      app-vis-servers.png

  2. Retrieve the Application Visibility integration from the Real User Collector component. To do this, perform the following steps:
    1. In the Real User Analyzer, open Administration > Data flow settings > Custom Fields page.
    2. Scroll down to the bottom and expand the Trace [system default] element.
    3. On the Action menu, click Add new rule.
    4. From the Format list, select Default (catch all), and click Next.
    5. From the Source field list, select Primitive Custom Field Extractions.
    6. From the Primitive custom fields list, select the Application Visibility field with the Real User Collector instance. For example, applicationVisibility ([myCollector]). Click Next.
    7. On the next page, click Done.
  3. To verify the integration, ensure that the Real User Analyzer is picking up the Application Visibility custom fields from Real User Collector component. To do this, perform the following steps:
    1. In the Real User Analyzer, open the Reference Lists page.
    2. In the Object custom fields section, click Trace (object-level).
      If active Application Diagnostics agents exist for .NET or Java tracing, and if the integration is set up correctly, you will see several Visibility IDs. These will show up a few minutes after the integration setup.

Results

You can now drill down from the Session Overview or Session Browser a specific transaction trace, or locate the user session from a specific transaction trace:

  • In BMC Application Diagnostics Trace Details window, click the View session details  button to open one of the following windows (depending on configuration):
    • Session Overview page, in the Object Overview section.
    • Session Browser page, in the Real User Analyzer.
  • In a BMC Real End User Experience Monitoring session, click the View trace details button to open the diagnostics data for the transaction trace in the BMC Application Diagnostics Trace Details window.

Related topics

Reviewing-the-diagnostics-data-for-a-trace

From BMC Real End User Experience Monitoring online technical documentation:

 

 

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