Service Auto Creation Rules
Last updated – 13 April, 2026
Note: This feature is currently in Beta. To become a Beta participant, contact Customer Success Manager.
Service Auto Creation Rules enable 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
- In LogicMonitor, navigate to Services.
- Select
and select Multiple services, via a new Auto-Creation Rule.
- 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.

- Under Step 1: Select members properties, do the following:
- 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 do not currently exist on any resource.
Once those properties are assigned to resources, services are created automatically if the rule is active.
Note:- You cannot use restricted or sensitive property keys as Group by fields.
- Restricted keys include properties such as
predef.externalResourceID,system.categories,system.groups,system.ips,system.pushmodules, and so on. - Sensitive keys include any credentials or secrets, such as
auth.key,azure.secretkey,user.pass,admin.password,aws.accesskeyand similar credentials. - If you attempt to use a sensitive or restricted key, LogicMonitor will display an error, “Custom property key cannot include sensitive or restricted keys.”
For example, to prepare for future resource onboarding, a user creates a service template using the property keycountry1. Although this key is not currently assigned to any resources, it enables the rule to group resources automatically once they are added.


- In the Filter by field, define filters to include specific instances or resources.
- Filters also support non-existent property keys and values. This enables you to predefine logic even if the resource data hasn’t been added yet.
Note: Both grouping and filtering values cannot be modified after rule creation.
- In the Service naming pattern field, define the service names by modifying the text and property references as needed.


Note:
- Service names support the same character rules as LogicMonitor resource names.
- All characters are valid and accepted in the service name except the following: * < ? , ; `(backtick) (\n)line breaks.
- 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:
| Service Details | Description |
| Service Name | Displays the name of the services created. |
| Resources | Displays the number of resources associated with each service. |
| Service criticality | Displays the default criticality level assigned to each service (for example, Low, Medium, High). You can customize this value. |
| Create status | Displays the status of the service creation process. |
| Status detail | Displays detailed status messages, including any errors or warnings. |
- 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.

- (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.

- Select Preview to review the resulting service group structure.

- In the Other service groups to add these services to field, specify additional service groups.
- Add custom key-value pairs to the New properties section if needed for LogicModule integration.
- Select Next: Save rule and add metrics to finalize the auto-creation rule.


