CheckCentral can parse anything you send to it, which means you can monitor more than just backups! With this script, you can send the status of your HP RAID volumes to CheckCentral daily and get notified if anything is amiss.
In CheckCentral, go to Organization > API.
Click "Add Token."
Give the token a name, e.g.
.
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 .ssacli.exe can be located in different directories depending on the version, so update the directory path on line 16 if needed.
Run the script. You'll now see an unmatched activity in CheckCentral.
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 "
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.
Your Check so far will look something like this:
Navigate to the next step in CheckCentral by clicking the "Next" button or the tab name.
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.
The initial expectation time is set by the first email message that is received and processed by its Check. (For example, if a notification email arrives at noon and its Check is set for every half hour, it will expect another notification email at 12:30.)
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.
The Matching step is what matches a notification email to its specific Check. It's also where you'll set the notification's CheckCentral destination email. For email-based notifications, this email can be used for quick matching. Because this is an API-created activity, other Matching Rules are needed.
A Matching Rule is created by default with the Subject of the message crafted by the earlier test run of the script. The "Subject" "Is Exactly" dropdowns and the text
are displayed, appended with the Computer Name of the computer running the script.
Leave the "HP 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."
The email address will appear different based on your organization name and the name you specified for your check.
The previous Matching step identifies the incoming message to the Check. The Status step looks for indicators of what type of notification you're receiving (e.g. The job was successfully run, it failed, or there were some issues.)
Leave the Default Status on "Failure."
The "Success Criteria" section is where you'll set the criteria that will mark an activity as successful.
The output from omreport will show
(where # is the number of volumes reported).
Set the rule to "Body Text" "Complex Match" and then type
(with quotes included) in the empty text field, replacing the
with the number of volumes. For RAID controllers with only one volume, use
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.
Notifications are simply how you want to be informed of Check Failures, Warnings, and some other Status changes.
Email, push, chat and other software can be integrated as well as ticketing systems, allowing for automatic ticket creation and management.
Further configuration is required for each to function and is done via the Notifications tab in the main menu. They can be configured before or after Check creation.
For more understanding of Notification setup, see the
CheckCentral Beginner's Guide (Notifications).
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.
Under "Recent Messages Now Matched" your previously unmatched activity will be displayed with a green Status indicator (assuming the full number of volumes returned an "OK").
Close the Test window.
Click the "Save Check" button.
Now that the script is configured and the check is created, you'll want to create a Scheduled Task on the machine to run the script daily. The Scheduled Task should run the following command:
powershell.exe -ExecutionPolicy Bypass -File "path-to-the-script"
.
Binary Fortress has spent 17 years in pursuit of one goal: create software to make life easier. Our software ranges from display management and system enhancement utilities to monitoring tools and digital signage. IT administrators, professional gamers, coffee-shop owners, and MSPs all rely on Binary Fortress to make their days better, and their lives easier.
Copyright © 2007-2024 Binary Fortress Software, all rights reserved.
The Binary Fortress logo is a trademark of Binary Fortress Software.
The CheckCentral logo is a trademark of Binary Fortress Software.
Binary Fortress Software
1000 Innovation Drive, Suite 500
Kanata, Ontario, Canada
K2K3E7
https://www.binaryfortress.com
