Load balancer blueprints

BMC Helix AIOps offers several out-of-the-box blueprints that are ready to use and consist of rule-based templates to create services. Find the details of the default application blueprints in the following sections:

Related topics

Creating-service-blueprints

Defining-a-service

FAQ


Default Blueprint for Load Balancer

Use this application blueprint to create business services to monitor a load balancer deployment.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Load Balancer Instance
  • Traversal path and connected nodes: Associated Load Balancer member nodes interconnected with the Host, Software Instance, Host, Database, Network Interface, Network Device, and so on, as shown in the following image:
    load_balancer_2.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. When creating the service model, the service designer must select the name of the Load Balancer Service as input.
      load_balancer_2.0_filter_part1.png

    • The default Filter by Kind link rule is enabled between the Virtual Machine and Host node connection, as shown in the following image:
      load_balancer_2.0_filter_part2.png

Earlier version of the blueprint

Click here to expand.

Discontinued versionStarting with version 24.1.01, BMC has released version 2.0 of this out-of-the-box blueprint and no longer supports version 1.0. However, if you want to continue using version 1.0, export the blueprint from the earlier version of BMC Helix AIOps and import it into the current version of BMC Helix AIOps.

Version 1.0 nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Load Balancer Instance
  • Traversal path and connected nodes: Associated Load Balancer member nodes interconnected with Host, Network Interfaces, and Network Device, as shown in the following image:
    load_balancer_1.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. When creating the service model, the service designer must select the name of the Load Balancer Service as input.
      load_balancer_1.0_filter_part1.png

    • The default Filter by Kind link rule is enabled between the Load Balancer Service and Load Balancer Pool, Load Balancer Pool and Load Balancer Member, and Load Balancer Member and Host nodes, as shown in the following image:
      load_balancer_1.0_filter_part2.png


Where to go from here

Creating-service-models

 

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