FAQs

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

  1. No. You can only delete blueprints that are not associated with any services. However, you can remove the blueprint from the associated services and delete it.

  2. No. You can only delete blueprints from BMC Helix AIOps. However, you can unpublish a blueprint from BMC Helix Discovery.

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

    • 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 Team Open link for assistance.
    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.
  6. Enable the Configuration > Manage Situations > Advanced options > Show policy-based Situations. For more information, see Configuring ML-based situations.

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

  8. At least two events are required to create a situation.

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

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

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

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

Was this page helpful? Yes No Submitting... Thank you

Comments