Important Starting from version 22.2, the documentation for BMC Helix Intelligent Integrations and Developer Tools resides in a separate space: BMC Helix Intelligent Integrations.

FAQs


Here are the answers to some frequently asked questions about BMC Helix AIOps. 

  1. The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  2. The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  3. Which integrations are available out-of-the-box in BMC Helix Intelligent Integrations?

    The following out-of-the-box integrations are available with BMC Helix Intelligent Integrations. If you plan to integrate one of the following products, configure the appropriate integration and start receiving data.

  4. Can I integrate any third-party product for which out-of-the-box integration is not available?

    Yes. Use BMC Helix Developer Tools to build custom integrations for the third-party products for which the out-of-the-box integrations are not available.

  5. Can I perform ML-based root cause isolation on impacted services?

    Yes, monitor all the services on the Entities page, click an impacted service and perform ML-based root cause isolation. For more information, see Performing-ML-based-root-cause-isolation-of-an-impacted-service.

  6. What should I do if I see a blank UI page on the BMC Helix AIOps console?
    • Check if you have the required permissions to view data in BMC Helix AIOps. For more information, see Roles-and-permissions.
    • Check if you have subscribed to at least one of the data providers that work with BMC Helix AIOps. You will see data only if you have subscribed to one or more data providers.
    • If you are a new customer, contact BMC Sales Teamfor assistance.

  7. What should I do to see the ML-based situations listed in the Overview > Situations and Situation pages?
    1. Contact BMC Sales Team to subscribe to use this feature. 
    2. Enable the AIOps Situations option from the Configuration > Manage Product Features page. For more information, see Enabling-the-AIOps-features.
  8. What should I do to see the policy-based situations along with the ML-based situations in the console?

    Enable the Configuration > Manage Situations > Advanced options > Show policy-based Situations. For more information, see Configuring-ML-based-situations.

  9. What should I do to stop seeing the policy-based situations along with the ML-based situations in the console?

    Do one of the following steps: 

    • Go to the Configuration > Manage Situations > Advanced options and disable Show policy-based Situations option.
      For more information, see Configuring-ML-based-situations.
    • Go to the Configuration > Manage Situations and click Reset to Default.

    Note

    Use the Reset to Default option, only if you want to reset all the settings on the page to the default values. To hide only the policy-based Situations, disable the Show policy-based Situations option.

  10. What is the minimum number of events required to create a situation?

    At least two events are required to create a situation.

  11. What are the pre-requisites for creating ML-based situations?

    The service model and its topology, event, and event types are required to create ML-based situations.

  12. What properties of an event are used to build the event signature that is used while creating an ML-based situation?

    Preprocessed event message and the event entity type such as CPU usage in VM, Response time in tomcat5, and so on are used to create the event signature.

  13. How is an event signature created for a custom-class event that is received from a third-party product?

    Based on the event message and its entity type, the algorithm decides the event slots that will be used to create the event signature.

  14. What is the significance of an event signature?

    Event signatures are used to uniquely identify similar events and create a preliminary group. These event signatures further leverage service topology, temporal, and knowledge graph dimensions to assign events to respective situations.

 

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