Creating a disk monitoring metric extension for Exadata Compute Nodes
By Mike Chafin on Aug 23, 2013
It is highly desirable to monitor the Exadata Compute node disks for current failures or degraded performance. By using the Enterprise Manager metric extension functionality Compute nodes can be monitored for these conditions and an alert created in the event of an issue. The following steps will guide you through this process
$ ./emcli login -username=sysmanEnter password :Login successful
$ ./emcli create_credential_set -set_name=root_monitoring -target_type=cluster -supported_cred_types=HostCreds -descript=root_monitoring monitoringCreate credential set for target type host
Setup--> Security-->Monitoring CredentialsSelect Cluster and the push the "Manage Monitoring Credentials" buttonFind the target you want to test on with the credential set defined in step 2( In this case root_monitoring)Highlight the credential set and push the "Set Credentials" button. Enter the credentials and use the test and save button to ensure they are correctly defined
Select the create button
Target type select "Host"Name "Compute_Node_Disk_Monitoring"Display Name "Compute Node Disk Monitoring"Adapter "OS Command - Multiple Columns"Data Collection "Enabled"Repeat Every "5 Minutes"Use of Metric Data "Alerting and Historical Trending"Upload Interval "1 Collections"Select the Next Button
On your local machine create a file called megaclicommand.sh that contains the following/opt/MegaRAID/MegaCli/MegaCli64 AdpAllInfo -aALL | grep "Virtual Drives" -A 6 | grep -w 'Degraded\|Critical\|Offline\|Failed' | sed 's/Degraded/Virtual Drives Degrades/g' | sed 's/Offline/Virtual Drives Offline/g' | sed 's/Critical Disks/Critical Physical Disks/g' | sed 's/Failed Disks/Failed Physical Disks/g'
Command "/bin/sh"Script "%scriptsDir%/megaclicommand.sh"Delimiter ":"
Select the upload button and select the file created in step 6Click okay and one back to the Create New:Adapter page select the "Next" button
Column one should be setup as:Name "Type"Display Name "Type"Column Type "Key Column"Value Type "String"Metric Category "Fault"Column two should be setup as:Name "Value"Display Name "Value"Column Type "Data Column"Value Type "Number"Metric Category "Fault"Comparison Operator ">"Critical "0"After Setting up the two column select the next button
Select the “Specify Credential Set” radio buttonIn the drop down box select the credential set created in step 1Click the next button
Add a target to test with in the “Test Targets” sectionClick the “Run Test” button and ensure that results are displayed properly in the “Test Results” box.The results should be similar to belowType ValueVirtual Drives Degrades 0Virtual Drives Offline 0Critical Physical Disks 0Failed Physical Disks 0
12. Next the the Metric Extension must be saved as a deployable draft. This is accomplished on the main metric extension page. This allows the metric to be deployed to targets for testing. However at this stage only the developer has access to publish the metric. After satisfactory testing is completed the metric is then published. This is once again accomplished from the main metric extension page.
Now click the “Create Rule Set..” button
2. On the Create Rule Set screen enter the following information