1 / 36

Monitoring Your Data Center

Monitoring Your Data Center. Objectives. After completing this lesson, you should be able to: Identify out-of-box monitoring features Change metric settings Create and apply monitoring templates Use notifications Create notification rules Create User-Defined Metrics (UDMs) Use blackouts.

kort
Download Presentation

Monitoring Your Data Center

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Monitoring Your Data Center

  2. Objectives • After completing this lesson, you should be able to: • Identify out-of-box monitoring features • Change metric settings • Create and apply monitoring templates • Use notifications • Create notification rules • Create User-Defined Metrics (UDMs) • Use blackouts

  3. Out-of-Box Monitoring • You can use the following out-of-box monitoring features: • Predefined metrics for all monitored targets • Historical collections for trend analysis and reporting • Access to real-time performance charts • E-mail notification for critical alerts

  4. Metric Thresholds • Metric thresholds are the values that mark the boundary for the metric. If the metric crosses this value, an alert is triggered. • You can set threshold values for the following: • Warning threshold: The area is still functional, but needs attention. • Critical threshold: This is indicative of imminent problems and requires immediate action.

  5. Changing Metric Thresholds

  6. Changing Collection Schedules

  7. Corrective Actions • Corrective actions are a way to specify an automated response to an alert. • You can define different corrective actions for warning and critical alerts. • By default, the corrective action task runs on the target on which the alert is triggered. • You can also define multitask corrective actions that run against other targets.

  8. Defining Corrective Actions • From the Metric and Policy Settings page, click the Edit icon for the metric for which you want to define the corrective action. • Click the Add button to define a corrective action. • Select from different types of corrective actions that you can define. • Click the Continue button after selecting the corrective action type. • On the General page, give a proper name for corrective action. • Click the Parameters tab.

  9. Defining Corrective Actions • Select the command type. • Enter the command or the script depending on the command type.

  10. Defining Corrective Actions • Click the Credential tab. • Specify the preferred credentials. • Click Continue.

  11. Trivia • What minimum target-level privileges do you need to have to perform any metric threshold changes? • Options: • FULL • OPERATOR • VIEW • None • What are the two different types of thresholds?

  12. Apply Apply Apply Apply Monitoring Templates Pre-Template Post-Template Target 1 Target 1 Template 1 Target 2 Target 2 ProductionEnvironmentTarget Target 3 Target 3 Template 2 Target 4 Target 4

  13. Creating Monitoring Templates • Click the Setup link in the upper-right corner. • Select Monitoring Templates from the left navigation bar. • Click the Create button. • Select the target that has the monitoring settings that you want to use in the template. • Specify a name for the template. • Select the metrics and the policies, and change the thresholds or the collection schedules. • Apply the template.

  14. Applying Monitoring Templates • Applying templates: • You need at least OPERATOR privileges on the destination targets. • The target can have multiple templates: “Last one wins.” • Only those metrics defined in the template will override the metrics in the destination target. • There is no link between target and template. • The target can prevent template override on a per metric basis. • After applying the template, check the Pending Apply Operations link. • Check “Past Apply Operations” for history of past template apply operations.

  15. Applying Monitoring Templates • Option 1: “Apply threshold settings for monitored objects common to both template and target” • Example: Filesystem Space Available (%) Template Destination Target Mount Pt Warning Critical Mount Pt Warning Critical /u1 30 20 /u1 31 21 /u2 35 25 /u3 36 26 All others 20 10 All others 21 11 Mount Pt Warning Critical Target settings after applying template  /u1 30* 20* /u3 36 26 *Changed values All others 20* 10*

  16. Applying Monitoring Templates • Option 2: “Duplicate threshold settings on target” • Example: Filesystem Space Available (%) Template Destination Target Mount Pt Warning Critical Mount Pt Warning Critical /u1 30 20 /u1 31 21 /u2 35 25 /u3 36 26 All others 20 10 All others 21 11 Target settings after applying template  Mount Pt Warning Critical /u1 30* 20* /u2** 35 25 *Changed values **Values added /u3 dropped All others 20* 10*

  17. Applying Monitoring Templates • Option 2: “Duplicate threshold settings on target” • Example: Filesystem Space Available (%) Template Destination Target Mount Pt Warning Critical Mount Pt Warning Critical /u1 30 20 /u1 31 21 /u2 35 25 /u3 36 26 All others 21 11 Target settings after applying template  Mount Pt Warning Critical /u1 30* 20* *Changed values **Values added /u3 dropped “All Others” is untouched /u2** 35 25 All others 21 11

  18. Using Notifications • Notifications enable the administrators to resolve issues quickly by notifying them when an alert is triggered. • As an administrator, you must define the following to receive notifications: • E-mail addresses • Notification schedule • Notification rules • The Super Administrator must set the SMTP gateway to use notifications.

  19. Notification Methods

  20. Defining E-Mail Addresses

  21. Notification Schedule

  22. Notification Rules

  23. Creating Notification Rules • You can create additional notification rules and also edit or view the existing notifications rules.

  24. Trivia • Match the following:

  25. User-Defined Metrics • Using User-Defined Metrics (UDMs), you can widen the scope of monitoring the conditions that are specific to your environment. • There are two types of User-Defined Metrics: • Operating System (OS) User-Defined Metrics • SQL User-Defined Metrics

  26. Creating Operating System User-Defined Metrics • You need to perform the following two steps to create Operating System User-Defined Metrics: • Create your OS monitoring script. • Register the script as a User-Defined Metric.

  27. Creating Your OS Monitoring Script • The script can be written in any scripting language that is supported on the platform you are monitoring. • Place the script in a directory where the agent has full access privileges to read and execute. • The script should perform the following functions: • Check the status of the monitored object. • Evaluate the results of the status check. • Return results to Grid Control in the proper format. em_result=<numeric value> em_message=<message describing script result>

  28. Registering the Script

  29. Using SQL User-Defined Metrics • SQL User-Defined Metrics (SQL UDMs) enable you to extend monitoring of databases by plugging in your own SQL queries to monitor conditions that are specific to your environment. • The values returned by your queries can be compared against the thresholds that you specify, and alerts are triggered when thresholds are crossed. • In Oracle Enterprise Manager 10g Release 2, SQL UDMs have been enhanced in the following ways: • SQL queries for SQL UDMs can return two-column, multirow values. • The format of the alert message can be customized. • A Test button is provided to enable verification of the SQL query and credentials.

  30. Creating SQL User-Defined Metrics

  31. Creating SQL User-Defined Metrics

  32. EBiz Host AS ……. Oracle Management Services DB Agent Servers Storage Network Software AS OCS eBiz Database Enterprise config management Application pref management EBiz Host AS ……. Precision system monitoring Administration DB Agent Infrastructure (Jobs, Alerts, and so on.) eBiz Host AS ……. DB Agent Blackouts Targets Manage from anywhere HTTP/S HTML console HTTP/S Mobile device JDBC HTTP/S HTTP/S Blackout Oracle Management Repository Portals Firewall

  33. Creating Blackout

  34. Ending Blackout

  35. Summary • In this lesson, you should have learned how to: • Identify out-of-box monitoring features • Change metric settings • Create and apply monitoring templates • Use notifications • Create notification rules • Create User-Defined Metrics • Use blackouts

  36. Practice 11 Overview: Monitoring Your Data Center • This practice covers the following topics: • Changing the Metric Collection Schedule • Changing Metric Thresholds • Defining Corrective Actions • Creating SQL User-Defined Metrics • Creating Monitoring Templates • Setting Up E-Mail Addresses • Defining Notification Schedule • Subscribing to Notification Rules • Creating Blackouts

More Related