Using out-of-the-box blueprints


BMC Helix AIOps provides out-of-the-box blueprints, which service designers can use as is to create services within a few minutes. 

Out-of-the-box blueprints

A BMC Helix AIOps subscription comes with out-of-the-box blueprints. However, by default, these blueprints are not visible on the BMC Helix AIOps console. As a tenant administrator, you must import and enable these blueprints. After you import the out-of-the-box blueprints, they are listed with the prefix Default as shown in the following table. These default blueprints are available for creating a service only after you enable them. For example, if you want to use the Default Blueprint for Dynatrace to monitor the application performance of a Retail service, it must be enabled first. If a blueprint has multiple versions, the version is added to the Description field, for example, Using Dynatrace Applications, v2.

The following default blueprints are available out of the box in the BMC Helix environment:

Category

Blueprints

Default Blueprint for OTel

Default Blueprint for Apache Tomcat Application Server

Default Blueprint for Red Hat JBoss and its connections

Default Blueprint for Microsoft IIS Webserver

Default Blueprint for Microsoft SharePoint Server Name

Default Blueprint for Microsoft Skype for Business Site

Default Blueprint for SAP

Default Blueprint for Appdynamics Applications

Default Blueprint for Dynatrace applications

Default Blueprint for Container Infrastructure Services

Default Blueprint for Kubernetes Infrastructure

Default Blueprint for Kubernetes to VM to Switch

Default Blueprint for OpenShift Namespace

Default Blueprint for Database to Application

Default Blueprint for Cloud Service

Default Blueprint for Cloud Region

Default Blueprint for Virtual Hosts With Cloud Associations

Infrastructure (On-Premises)

Default Blueprint for Control-M Enterprise Manager

Default Blueprint for Microsoft Cluster Name

Default Blueprint for Oracle WebLogic Cluster

Default Blueprint for vCenter Cluster Name

Default Blueprint using Load Balancer Service Name

Default Blueprint for Mainframe LPAR to connected Softwares

Default Blueprint for Network Device and its connections

Default Blueprint for Network Device to Host

Default Blueprint for Physical Host to Network Device

Default Blueprint for Virtual Host to Network Device

Default Blueprint for Wireless LAN Controller Network Device Name

Default Blueprint for Host to Storage linkage

Default Blueprint for Storage System

Default Blueprint using Tags

Default Blueprint for Genetec Security Center Name

To import and enable the out-of-the box blueprints

  1. Select Configurations > Manage Service Blueprints.
  2. On the Service Blueprints page, from the action menuaction_menu.png, select Import BMC default Blueprints.
    The imported blueprints appear on the Service Blueprints page. These blueprints are indicated by ootb_bluprints.pngin the Provider column.
  3. Choose a service blueprint from the list and select Action > Enable
  4. Click Hide disabled to view the list of all the enabled service blueprints.
  5. Check for the newly enabled blueprint in the list.

To create a custom blueprint from an existing blueprint

  1. On the Service Blueprints page, from the Action menu for a blueprint, select Create new Blueprint from.
  2. Edit the blueprint rules as required and click Next Step (Preview result) to preview the model.
  3. Save the custom blueprint.

Where to go from here

Creating-service-models

 

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