• Download the script: dell_omreport_raid_check.ps1
• In CheckCentral, go to Organization > API.

• Click "Add Token."

• Give the token a name, e.g.

  SERVER01 Dell RAID Script

  .
• Select "createActivities Only" in the Access Level drop-down and click Save.

• Copy the token, and paste it in the $apiToken variable on line 11 of the script.

• On line 14 of the script, set the RAID Controller ID. If there's only one in the machine, this will most likely be

  0

  .
• Run the script. You'll now see an unmatched activity in CheckCentral.
• Configure this script to run on a machine somewhere as a regularly scheduled task. (Daily in this example)

• In CheckCentral, go to Activities.

• Select "Unmatched" from the Matched dropdown selector and then click the "Filter" button. The results will show below.

• Click the "Create Check" link next to the relevant activity.

• Leave the Name as is.
• Select an existing Check Group or create a new one by clicking "group_icon.png

  Add Check Group

  ".
• Select an existing Label or create a new one by typing the name in the text field of the dropdown (optional).
• Add a description (optional).
The Asset ID is used exclusively with certain ticketing systems and is not required for Checks. Asset ID details and ticketing systems are more fully covered by other documents (e.g. Halo Integration (asset ID).)
• Leave the Asset ID blank.

• Leave "Scheduled" selected as we will be running the script regularly.
• Assuming you'll run the script daily, leave the Expected Interval on "1" "Day(s)." If you plan to run the script on another interval, adjust accordingly.

• Leave the Set as Overdue setting at "After 30 Minutes." If the script notification email is not received after this amount of time has been exceeded, the Check will be marked as a failure. Leave Custom Schedule de-selected.

Dell RAID Status:

• Leave the "Dell RAID Status" Matching Rule as is. You can delete the other email address Matching Rule by clicking the trashcan icon, but it is not required.
• Leave Condense Whitespace and Combine Attachments enabled and the matching modifier set to "All."

• Leave the Default Status on "Failure." The "Success Criteria" section is where you'll set the criteria that will mark an activity as successful.
• Click

  

  Add Success Rule

  . The output from omreport will show

  "Status : Ok"{#}

  (where # is the number of volumes reported).
• Set the rule to "Body Text" "Complex Match" and then type

  "Status : Ok"{#}

  (with quotes included) in the empty text field, replacing the

  #

  with the number of volumes. For omreports with only one volume, use

  "Status : Ok"

  instead (without

  {#}

  ).
• The "Warning Criteria" section is where you'll set the criteria that will mark an activity with a warning. Because there is no warning criteria for this Check, we do not add a rule.
• Leave the Condense Whitespace and Combine Attachments checkboxes enabled.

• Select the desired means of Notification. If in doubt of the selections here, leave the defaults.

• To confirm the activity now matches the check, click the Test button.

• Close the Test window.
• Click the "Save Check" button.

We're pleased to announce that we've added GitLab as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

GitLab External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

We're pleased to announce that we've added GitHub as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

GitHub External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

We're pleased to announce that we've added ConnectWise Manage as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

ConnectWise External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

We're pleased to announce that we've added Freshdesk as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

Freshdesk External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

We're pleased to announce that we've added Atera as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

Atera External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!