This page outlines key guidelines for designing efficient and manageable resource nodes within OpsRamp service maps. A service map resource node shows the availability status of a collection of resources that are part of a business service. When configuring these nodes, prioritize the aggregation of resources by type or function.

It is strongly recommended to group resources of similar type or function into a single resource node. Example: Consolidate all MySQL resources supporting the “Acme Web Application” under a single “MySQL” node, regardless of instance count.

Benefits of this approach:

  • Easier to define a single availability rule for all similar resources (e.g., all MySQL resources).
  • New matching resources are automatically added to the node.
  • Non-matching resources are automatically removed from the node.
  • This principle applies to other resource types (e.g., Cassandra).
  • Enables efficient service map scaling.
  • Results in faster service map loading.
  • Facilitates easier service map management and updates.