Compound Conditions

What are the Compound Conditions in NinjaOne?

Compound Conditions in NinjaOne are combinations of multiple criteria that increase the granularity of how alerts are triggered and actions are executed. They allow administrators to define more precise rules for device targeting, monitoring, and automation.

How are compound conditions used in NinjaOne?

Compound conditions in NinjaOne are used in policies. When a condition is met, you can define actions to take, like opening a ticket, running an automation, or sending a notification.

Strategy: Create a compound condition to monitor the DHCP service, only if that service exists in the endpoint

For this example, we will create a compound condition to send an alert when the DHCP service is down on a server with the DHCP service present. We will use the Windows Server policy.

Follow the steps below to create the compound condition.

  1. Edit the policy of your preference, for this example we will use the Windows server policy.
  2. Click Compound Conditions.
  3. Click +Add A screenshot showing how to create a compound condition
  4. After the “Add a compound condition” dialog box appears, click + Add condition and select Windows Service from the drop-down menu. The Add device condition appears. A screenshot showing how to add a compound condition
  5. From the Windows services drop-down menu, select “DHCPServer”.
  6. From the Trigger When drop-down menu, select “Exists”.
  7. Click Apply. A screenshot showing how to add a service condition
  8. Repeat from step 4, but this time, instead of selecting “Exists” from the Trigger When drop-down, select “Down”.
  9. Click Settings on the left side menu.
  10. Fill in the compound condition settings, like name, if/when it will be auto-reset, etc. Filling this menu is mandatory. A screenshot showing the settings of a compound condition
  11. Click Notifications on the left side menu and fill in the severity, priority, notifications, and ticketing rules if a ticket is required for this condition. A screenshot showing how to add a compound condition
  12. Optionally, you can create an automation to run when this condition is met, however, we will skip this step for this example.
  13. Click Conditions on the left side menu and make sure you select “all conditions are true” on the Trigger when drop-down menu. A screenshot showing how to edit a compound condition
  14. Click Apply.
  15. Save your policy.

Note: With condition monitoring through compound conditions, you can use the same general Windows server policy and check the DHCP service status only if the service exists on the endpoint. Without this feature, you would need to create a separate policy specifically for DHCP servers.

FAQ

Compound conditions in NinjaOne are customizable logic sets that evaluate multiple criteria to control how and when alerts are triggered or actions are executed. Designed for use in policies, they enable precise targeting, automation, and monitoring across managed devices

Simple conditions allow you to define a single rule that triggers an action. Compound conditions, on the other hand, let you combine multiple rules, so the action is triggered when one or more of them are met, depending on how they’re configured.

With simple conditions, you can choose from a list of native conditions (e.g., disk free space, CPU, memory…) or create custom conditions using templates or custom fields. Compound conditions, on the other hand, cannot be selected from the native conditions or templates, they must be built from scratch using criteria such as script results, custom fields, installed or uninstalled software, or the status of a Windows service.

Common use cases are conditions that happen when some specific software is installed or is not installed, or when some services are present, or not present, like in the example shown in the document.

The available logical operators are AND (all conditions are true) and OR (any condition is true). You can select the operator in the Conditions tab of the Compound Condition editor, under the “Trigger when” field.

In NinjaOne, Compound Conditions include an Automations tab where you can select any available automation in your tenant to run when the condition is met. NinjaOne provides many pre-built native automations, but you can also create your own.

×

See NinjaOne in action!

By submitting this form, I accept NinjaOne's privacy policy.