Application performance monitoring blueprints

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

Related topics

Using-out-of-the-box-blueprints

Creating-service-blueprints

FAQ

Default Blueprint for Appdynamics Applications

Use this default blueprint to create a business application or business service.

Important

If this blueprint has multiple versions, the version is added to the Description field, for example, Using Appdynamics Application, v2.

Before you begin

Discover AppDynamics infrastructure data through BMC Helix Discoveryor ingest it through the BMC Helix Intelligent Integrations connector.

Nodes, connections, and filters

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

  • Start node: Software Cluster node in BMC Helix Discovery representing an application defined in AppDynamics. 
  • Traversal path and connected nodes: Associated Software Cluster, Software Components, Software Instances, Databases, Hosts, Cluster, Coupling Facility, MF Part, Virtual Machine, and so on, as shown in the following image:
    app_dynamics_2.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter applications that match the AppDynamics(.*) key. Additionally, the service designer must select the name of AppDynamics applications as input.
      app_dynamics_2.0_filter_rules.png

    • The default Filter by Kind link rule is enabled, as shown in the following image between the Software Cluster to Software Component and the Virtual Machine and Host node connections:
      app_dynamics_2.0_filter_rules_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: Software Cluster node in BMC Helix Discovery representing an application defined in AppDynamics. 
  • Traversal path and connected nodes: Associated Software Cluster, Software components, Software instance, Hosts, Network Interfaces, and Network Devices, as shown in the following image:
    app_dynamics_1.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter applications that match the AppDynamics(.*) key. Additionally, the service designer must select the name of AppDynamics applications as input.
      app_dynamics_2.0_filter_rules.png

    • The default Filter by Kind link rule is enabled, as shown in the following image between the Software Cluster to Software Component and the Virtual Machine and Host node connections:
      app_dynamics_2.0_filter_rules_part2.png

Default Blueprint for Dynatrace applications

Use this default blueprint to create a business application or business service.

Important

If this blueprint has multiple versions, the version is added to the Description field, for example, Using Dynatrace Applications, v2.

Before you begin

Discover AppDynamics infrastructure data through BMC Helix Discovery or ingest it through the BMC Helix Intelligent Integrations connector.

Nodes, connections, and filters

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

  • Start node: Software Cluster in BMC Helix Discovery representing an application defined in Dynatrace.
  • Traversal path and connected nodes: Associated Software Clusters, Software Components, Software Instances, Databases, Hosts, Virtual Machine, Coupling Facility, MF Part, Cloud Service, Cloud Region, Cloud Provider, and so on, as shown in the following image:

dyna_trace_2.0.png

  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter applications that match the Dynatrace(.*) key. Additionally, the service designer must select the name of Dynatrace applications as input.
      dyna_trace_2.0_filter_rules_part1.png

    • The default Filter by Kind link rule is enabled, as shown in the following image between the Software Cluster to Software Component and the Virtual Machine and Host node connections:
      dyna_trace_2.0_filter_rules_part2.png

Earlier version of the blueprint

Click here to expand.

Discontinued version

Starting 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: Software Cluster in BMC Helix Discovery representing an application defined in Dynatrace.
  • Traversal path and connected nodes: Software instances, software components, hosts, and network interfaces and network devices, as shown in the following image:

    default_dyntrc_bp.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter applications that match the Dynatrace(.*) key. Additionally, the service designer must select the name of Dynatrace applications as input.
      dyna_trace_2.0_filter_rules_part1.png

    • The default Filter by Kind link rule is enabled, as shown in the following image between the Software Cluster to Software Component and the Virtual Machine and Host node connections:
      dyna_trace_2.0_filter_rules_part2.png


Where to go from here

Creating service models with blueprints

 

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