Unsupported contentThis version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Integrating with BMC TrueSight IT Data Analytics


While analyzing events on BMC TrueSight Operations Management, you can cross-launch into BMC TrueSight IT Data Analytics (or IT Data Analytics) to perform root-cause analysis. To be able to cross-launch, you need to first integrate BMC TrueSight Operations Management with IT Data Analytics.

Before you begin

For more information about this integration, see Additional integration details.

Integrating with BMC TrueSight IT Data Analytics

  1. Access the TrueSight console.
  2. From the navigation menu TS_navmenu.jpg, go to Administration > Components.
  3. On the Components page, click the action menu and select Add Component.
    ITDA_addComponent.PNG
    Select IT Data Analytics Server and enter the following details:

  4. Verify if the integration completed successfully.
    To do this, log on to IT Data Analytics, navigate to Administration > External Configurations, and verify if there is an entry with the external configuration, "True Sight Presentation Server". Note that the Presentation Server hosts the web-based console functions of BMC TrueSight Operations Management.
    Also, after you integrate, BMC TrueSight Infrastructure Management cells get automatically listed in the external configuration, which is created on IT Data Analytics. You can see the cells listed on IT Data Analytics by navigating to Administration > External Configurations, selecting the external configuration (which was automatically created after the integration), and then clicking View External Configuration view icon.jpg.

  

Notes

The following notes are important to keep in mind before deleting the IT Data Analytics registration details:

  • Ensure that you delete any data collectors or notifications on IT Data Analytics that are still communicating with BMC TrueSight Operations Management.
  • Ensure that IT Data Analytics is up and running.

This is important because otherwise the external configuration created on IT Data Analytics might not be deleted after you delete the component registration on BMC TrueSight Operations Management. If the external configuration still continues to show on IT Data Analytics, you can run a CLI command on IT Data Anlaytics to delete the external configuration. For more information, see CLI command in IT Data Analytics 2.0.

Cross-launching into BMC TrueSight IT Data Analytics

You can cross-launch into IT Data Analytics from applications and events available on BMC TrueSight Operations Management. Before you cross-launch into IT Data Analytics, it is important that you access the IT Data Analytics console and create a data collector for the following items:

  • Each device (host) included in the application from which you want to cross-launch.
  • Each host associated with the event from which you want to cross-launc

Data collectors are objects that help you collect data records (or events) from the target hosts and make it available for search and analysis. For more information, see Creating data collectors in IT Data Analytics 2.0. Creating data collectors beforehand ensures that you can search events after you cross-launch from BMC TrueSight Operations Management into IT Data Analytics.

To cross-launch into BMC TrueSight IT Data Analytics

  1. Access the TrueSight console.
  2. From the navigation menu, navigate to one of the following pages:

    Navigate to

    Click...

    Monitoring > Applications

    One of the application names, then click the action menu (vertical three dots) next to the application name, and then select Launch BMC TrueSight IT Data Analytics.

    Monitoring >Events

    The action menu next to one of the events that you want to investigate in IT Data Analytics, and then select Launch BMC TrueSight IT Data Analytics.

  3. Provide the user credentials for logging on to IT Data Analytics.

    You can see search results for one of the following search queries depending on whether you are cross-launching from an application or event.

    Search query with time range

    Notes

    If you cross-launch from an application

    ((HOST=HostName1.*) || HOST=HostName1) || (HOST=HostName2.*) || (HOST=HostName2)

    In the search query syntax, the following definitions apply:

    • HostName1 and HostName2 refer to the various host names associated with the application node.
    • ApplicationName refers to the name of the application.

    By default, the search query displays a list of host names (corresponding to the devices) associated with the application.

    If you have a large number of devices included in the application, then the default search query can be very long because it will have a large number of host names. Instead of searching for a list of host names to find event data associated with those hosts, you can search for the application context.

    To be able to search by the application context, you need to perform the following steps in IT Data Analytics:

    1. Navigate to BMC_ITDA_HOME%\custom\conf\server.
    2. Edit the olaengineCustomConfig.properties file and locate the console.crosslaunch.type=host property.
    3. Change the property value from host to app
    4. While creating data collectors for each of the devices (hosts) associated with the application, add a tag named ApplicationContext with the tag value set to the application name. For more information, see Creating data collectors in IT Data Analytics 2.0.

    Performing the preceding steps in IT Data Analytics is optional, however this can be useful to simplify the search query.

    (ApplicationContext="ApplicationName")

    Time range: 30 minutes before and 30 minutes after the last time when the application state changed.

    If you cross-launch from an event

    (HOST=hostName1 .*) || (HOST=HostName1)

    In the search query syntax, hostName1 refers to the host name associated with the event.

    Time range: 30 minutes before and 30 minutes after the event time.

Related topic

Network-ports

 

 

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