You add symptoms and recommendations to the alert definition so that when the host system compliance alert is generated, the symptoms appear as rules on the Compliance tab.

Before you begin

Configure the name, host object type, and alert impact setting for the alert so that it appears as a compliance standard. See Configure Basic Information for the Host Compliance Standard.

Procedure

  1. In the Alert Definition Workspace window, click Add Symptom Definitions and add the SSH symptom.
    1. From the Symptom Definition Type drop-down menu, select Metric / Property.
    2. In the Symptom search text box, enter SSH.
    3. Drag the symptom named SSH service is running to the symptoms workspace.

    If you add multiple symptoms for your own scenario, and you determine that the alert must trigger when any of the symptoms occur, you would select Any from the drop-down menu named This symptom set is true when.

  2. In the workspace navigation pane, click Add Recommendations, and create a recommendation for the standard.
    1. Click the plus sign to add a recommendation.
    2. Enter a name for the recommendation in the text box.

      For example, enter Turn on the SSH service. If you have a local runbook, you can provide a link to your local instructions.

    3. Click Save.
    4. Drag the recommendation to the workspace.

    In your own scenario, you can create multiple recommendations for the standard.

  3. Click Save.

Results

If the symptom condition becomes true, the symptom is triggered and the compliance alert is generated for the object. Because the alert definition includes the subtype named Compliance, the generated alert appears as a compliance standard on the Compliance tab.

What to do next

Review the Compliance tab for standards that indicate that other objects are out of compliance, including vCenter Server instances, virtual machines, distributed port groups, and distributed switches. See Compliance Tab.