Service Auto Creation Rules

Service Auto Creation Rules allow you to create and manage multiple services easily. You can select and group services based on property keys (cardinality), visualize the created services and their members and define the required service hierarchy. This streamlined approach simplifies service management and organization.

For more information on advanced features in Service Auto Creation Rules, refer to Using Conditional Count and Service Property.

Requirements for Adding Services Using Auto Creation Rules

You require administrator access to create service rules.

Adding Services Using Auto Creation Rules

1. In LogicMonitor, navigate to Services.
   
2. Select   and select Multiple services, via a new Auto-Creation Rule.
   
   

3. Under the Add multiple services from new Auto-Creation Rule: Members wizard, configure the rule basics.
   • In the Rule name field, enter a name for the rule.
   • (Optional) In the Description field, enter an appropriate description to help identify the rule later.
   • In the Default service criticality field, select a default value: Lowest, Low, Medium, High, or Highest.
     
     

4. In Step 1: Select members properties, select one option from the following:
   • Resource members only: Includes only resources as members in the service. The Group by field must use property keys that are defined at the resource level.
   • Individual instance members only: Includes only instances as members in the service. The Group by field must use property keys that are defined at the instance level.
   • Both resource and individual instance members: Includes both resources and instances in the service. The Group by field must use property keys that exist on both resources and instances.

5. In the Group by field, select one or more property keys to define service groupings. You can add up to five cardinality properties in the Group by field.
   In addition, you can use custom property keys if they don’t currently exist on any resource.
   Once those properties are assigned to resources, services are created automatically if the rule is active.

For example, to prepare for future resource onboarding, a user creates a service template using the property key country1. Although this key is not currently assigned to any resources, it enables the rule to group resources automatically once they are added.

6. In the Filter by field, define filters to include specific resources.
   Filters support non-existent property keys and values. This enables you to predefine logic even if the resource data hasn’t been added yet.

7. In the Service naming pattern field, define the service names by modifying the text and property references as needed.
   You can customize the name, by removing any unnecessary cardinality properties by selecting the  icon from the property tile in the preview area of the Service naming pattern.
   
   
   
   

8. Under Service preview, you can have a live preview of the service names based on the GroupBy, the FilterBy and the naming pattern. 
   • Select any previewed service to view its associated resources.
   • In the Services preview section, you can view the following information:

9. In the Default membership re-evaluation interval field, select how often LogicMonitor should re-check service membership:
   • Every 5 minutes — Ideal for environments where resource changes are frequent and need near real-time updates.
   • Every 30 minutes — Recommended for moderately dynamic environments.
   • Every 24 hours — Best suited for stable environments with minimal changes to service membership.

10. (Optional) Under Step 2: Service groups and properties, do the following:
    • Enable Create service groups for these services.
    • In the Parent service group field, enter the name of the parent service group to organize your services hierarchically.
    • In the Service group naming pattern field, select Insert Token to build dynamic folder names.
      
      Note: The forward slash / indicates folder hierarchy. Tokens are replaced with their actual property values.
      
      
      
    • Select Preview to review the resulting service group structure.
      
      
      
    • In the Other service groups to add these services to field, specify additional service groups.

11. Add custom key-value pairs to the New properties section if needed for LogicModule integration.

12. Select Next: Save rule and add metrics to finalize the auto-creation rule.