Documentation forServer Configuration Monitor
Monitoring server configurations is a key capability of Hybrid Cloud Observability Advanced and is also available in a standalone module, Server Configuration Monitor (SCM). Hybrid Cloud Observability Advanced and SCM are built on the self-hosted SolarWinds Platform.

Customize policy management in SCM

Starting with SCM 2023.3, you can define your own policies, check the logic of rules, and edit existing rules using a rule definition wizard. In addition, you can define data sources, expression on these data sources, and conditions using the Use the query builder. Alternatively, you can switch to a YAML editor if desired.

Add, copy, edit, and delete custom policies

Go to the Server Configuration Monitor Settings Policies tab to add, copy, edit, or delete SCM policies.

To add a custom policy, click Add, fill in the required fields, and click Save.
Add a custom policy to SCM

You can copy only out-of-the-box profiles (not custom policies), and then edit them to include your own policy definitions. To do so, select an out-of-the-box profile, and then click Copy.

SCM Settings - Copy an OOTB policy

After you copy a policy, edit it using the rule definition wizard (detailed in the Use the rule definition wizard to add rules, check the logic of rules, or edit rules section), and then click Save.

To delete a policy, select it from the list of policies and click Delete.

Delete a custom policy

In the pop-up dialog box, confirm that you want to delete the policy.

Confirm custom policy deletion

Use the rule definition wizard to add rules, check the logic of rules, or edit rules

To add rules, check the logic of rules, or edit rules, see the corresponding section below.

Add a rule

To add a rule to the policy:

  1. Select the policy from the Policies tab, and then click Edit.
    Edit policy rules

  2. In the Policy rules section, select Add rule.
    Add rule

  3. Add the rule details, including name, severity, display ID, and textual description of rule, how to check, and remediation. Then click Next.
    Add rule details

  4. Pre-condition with the Use the query builder, defining when the rule is applicable, and then click Next.
    Add pre-condition information

  5. Condition with the Use the query builder to define the rule logic itself, and then click Save.

    Add condition information to the rule

  6. Click Save again at the Policy level when prompted to do so.

    Any modifications you make to policies or rules are saved in the system only after you confirm them in the top Policy dialog. Until then, changes are made only in the browser.

Check the logic of a rule

To check the logic of a rule in the policy:

  1. From the Policies tab, select the policy you want to view, and then click View details.
    View policy details

  2. In the Policy rules section, use filters or the Search bar to find and select the rule you want to view.

  3. Click View rule to review the logic of the rule.
    View rule

  4. Review the Rule details, Pre-condition, and Condition tabs, and then click Close.
    Review rule details, pre-condition, and condition tabs

Edit a rule

To edit a rule in the policy:

  1. From the Policies tab, select the policy you want to edit, and click Edit.
    Edit policy rules

  2. In the Policy rules section, use filters or the Search bar to find and select the rule you want to edit.

  3. Click Edit rule (or Remove rule and then Save if you are certain you want to delete the rule from the policy).
    Edit rule

  4. Make desired updates to the rule details, pre-condition, or condition, and then click Save.
    Make desired changes to rule details, pre-condition, and condition

  5. Click Save again at the Policy level when prompted to do so.

    Any modifications you make to policies or rules are saved in the system only after you confirm them in the top Policy dialog. Until then, changes are made only in the browser.

Return to top

Understand and use the query builder

The query builder enables you to define:

  • Data sources including files, registry keys, database queries, and PowerShell scripts that map to SCM elements for polling during evaluation

    When selecting or creating data sources, keep in mind that:

  • Linux files and scripts are not currently supported as data sources.
  • Naming is mandatory for PowerShell scripts and database queries, but optional for registry keys and files.
  • Expression on these data sources using operators such as:

    • Contains a substring, or

    • Registry value is equal to 0

  • Conditions with logical operators, such as Contains a substring, AND registry value is equal to 0

The structure of the query builder is the same as that of the YAML format used in the policy engine.

Reuse data sources

Data sources can be reused in the scope of all rules in the same policy. They are de-duplicated, created, and removed from the system automatically based on the conditions when the policy is saved.

When editing a data source, clicking Save affects all of the usages and modifies all rules that use the data source. Save as copy, on the other hand, changes only the one edited occurrence.

Use operators

The operators used in the query builder are the same as those used in YAML.

  • For numerical comparison, use:

    • is less than

    • is greater than or equal to

    • is greater than

    • is less than or equal to

  • For string comparison, use:

    • is equal to

    • is not equal to

  • For string regex testing, use:

    • matches

  • For file/registry checking, use:

    • exists

    • not exists

Use the Translate special operator

You can use the Translate special operator to rewrite the evaluated status on an expression or a group. However, you can translate only from Passed or Failed and vice versa, or from either of those to Unknown.

Translate expression status drop-down menu

Translate expression result status dialog box - Toggle Translate Passed status - Use dropdown menu to select to translate to Failed or to Unknown status - Then click Save

The translation status is then indicated next to the expression or group.
Translate expression status indicator

Group logical operators

You cannot combine multiple logical operators on the same level. You must use parentheses to nest them separately. There is no limit on the nesting.

See an example of an invalid grouping of logical operators:
Example of invalid grouping of logical operators

See an example of a valid grouping of logical operators:
Example of a valid nested grouping of logical operators

Use the query builder

To use the query builder:

  1. Add or edit a policy, and then click Add rule; or select an existing rule and click Edit rule.

  2. On the Pre-condition or Condition tab, click the option to add a new pre-condition or condition.
    Click to add a new condition

  3. In the Define the condition dialog box, do one of the following:

    • Add an existing source from the drop-down menu and defining conditions. Then click Save. You will need to save again when prompted.
      Use data source and define conditions

    • Add a new data source by selecting Add new data source from the drop-down menu.
      Select Add new data source from the drop-down menu
      Then, in the Add new data source dialog box, add select a data source type from the drop-down menu and add relevant information. Then click Save. You will need to save again when prompted.
      Enter new data source information

    • Click Use other rule's status, select a rule, and select status is passed from the drop-down menu. Then click Save. You will need to save again when prompted.
      Use other rule's status - Select a rule from the drop-down menu
      Use other rule's status - Select status is passed from the drop-down menu

      Any modifications you make to policies or rules are saved in the system only after you confirm them in the top Policy dialog. Until then, changes are made only in the browser.

Return to top

Use the YAML editor

The YAML editor is available if the query builder does not meet your needs.

To use the YAML editor:

  1. Add or edit a policy, and then click Add rule; or select an existing rule and click Edit rule.

  2. On the Pre-condition or Condition tab, click the option to add a new pre-condition or condition.

  3. From the Query builder drop-down menu, select Yaml editor, define your pre-conditions or conditions, and click Save. If necessary, click Next, and then click Save again.
    Set pre-conditions or conditions using the YAML editor