Managing & Monitoring using EM12c

1. Managing & Monitoring using EM12c

2. Who am I? (Deepak Sharma) • SR. DBA for 5 years. • Worked on technologies like • Oracle 11g Grid Control, • Oracle 12c Cloud Control, • Oracle Configuration Manager • PeopleSoft Admin • SQL Server • Oracle Certified Professional. • Co-Founder of AIOUG-North India Chapter

3. Disclaimer: I am not a Guru. • All tips, recommendations and ideas are from reading, exploring and learning anyway that I can. I consider myself a B+ Student at best.

4. Introduction • OEM12c can manage and monitor your Enterprise Infrastructure & Applications across entire IT stack. • Monitoring your environment ensures that no component goes unwatched. • Through Events, Metrics and Incidents in EM, we can get a comprehensive picture of our environment at any point in time.

5. Best Practices • Best Practices to apply to monitor and manage your environment in EM12c: • Metric thresholds • Monitoring templates • Administration groups • Template collections • Synchronization schedules • Incident management

6. Metric Thresholds • Metric thresholds are the main features when we talk about monitoring. • They make us proactive to identify issues and address them in a timely manner. • EM12c contains multiple type of metrics.

7. Metric Thresholds Configuration • Metric threshold are configured in such a way that notification is sent via email to administrator. • Two level of severity: • Warning • Critical • Important components should be listed before defining your thresholds. • {can be database, listener, filesystem etc}

8. Metric Threshold Practical • To view all metrics of a database -> “Oracle Database -> Monitoring ->All Metrics”

9. Database Metrics & Threshold

10. Key Points • Threshold value should be obtained by gathering data during performance or load testing. • Define metrics for availability of target, such as database instance. • Values for CRITICAL thresholds should be chosen conservatively.

11. How to Set Metric thresholds • Example: Configure metrics for Tablespace Full alert. • Click Metric Category “Tablespaces Full” • Click on “Tablespace Space Used (%)” • Click on “Modify Threshold” button • Enter the values for the metrics.

12. Example

13. Example

14. Better Approach? • One-by-One method, easiest way to set metric for single target. • Number of targets = 100 databases ? • One-by-one approach will be difficult • Will be time consuming • Recommendation:- MONITORING TEMPLATES

15. Monitoring Templates • Monitoring Template is collection of metric thresholds for a specific target type. • Eg. A monitoring template can be created for Production database instances which may include: • Tablespace Space Used (%) >85/95 • Archive Area Space Used (%) >80/90 • Dump Area Used (%) > 90/95 • Status = DOWN

16. Key Points • Monitoring Templates standardized your monitoring settings. • Separate Monitoring Templates can be created for each target type. • Metric Thresholds set in your environment should not be fine-grained. • Don’t gratuitously create more templates than you need, because its just more work then to manage them.

17. Practical • To create monitoring template: • Login to EM12c Console • Enterprise -> Monitoring -> Monitoring Templates • On Monitoring Template page click “CREATE” button • Choose a representative target for monitoring settings • Eg. To create a database instance monitoring template, select an existing database instance to copy existing monitoring settings. • Alternatively , you may select a target type.

18. Practical • Enter a meaningful name for the template • Click the “Metric Threshold” tab • Enter or Modify the values for the metrics you want to set. • Click “OK” to save the template. • Non-required metrics can be removed all together. • If a threshold value is not set for any metric, no alerts will be sent for the metric.

19. Example

20. Example

21. Example

22. Example

23. Example

24. Example

25. Tips & Tricks • Collection schedule is another important point to remember while setting Metric threshold. • Collection schedule can be modified to meet operational goals. • If any metric is changed in monitoring template, template will have to be re-applied to its targets. • If metric threshold values are changed for a specific target, the changes are not synchronized to the monitoring template.

26. Administration Groups • Administration Groups automates the management and monitoring of targets by applying metrics to targets based on monitoring template collections. • Members are dynamically added to administration group automatically, based on a set of defined global properties. • Any target that matches the criteria is added to the group.

27. Planning the Hierarchy • Plan administration group hierarchy first. • Hierarchy consists of logically divided targets arranged in one or more levels. • Hierarchy is based global target properties. • Plan hierarchy to be in line with your Organization’s Operational & Monitoring standards.

28. Hierarchy Example • We want to create two groups one for Production and other for Non-Production based on “LifeCycle Status” property. • Further level of group can be decided based on any of the below mentioned target properties. • Department • Line of Business • Location • Contact • Decision to create more levels in hierarchy should depend on the monitoring characteristics of Groups.

29. Hierarchy Example

30. Key Points • There can be only one Administration group hierarchy. • A target can belong to only single group in hierarchy. • A target can not be added directly into a group. • Target properties can also be set at target discovery or promotion time. • Properties can be set through Console or using EMCLI command with help of “set_target_property_value” parameter.

31. Tips & Tricks • You can associate template collections to individual group. • Add multiple Monitoring templates to associate them to one Template collection. • Order in which Template collections are applied is Important. • Template collections at leaf level override metrics from the parent levels. • Template Collection from the parent levels are propagated to their respective subgroups.

32. Implementing Hierarchy • Click on “Setup -> Add Target -> Administration Groups”

33. Example

34. Example

35. Example

36. Joining Administration Groups • Next step is to add targets to Administration groups.

37. Example

38. Example

39. Template Collections • Template collection are used to provide consistent set of metrics to a group of similar targets. • Templates are created by target types. • Multiple Templates are bundled together to form a Template Collection. • Note:- A separate template collection is recommended for each node in hierarchy.

40. How to create Template Collection • Navigation: “Setup > Add Targets > Administration Group” • Click the “Template Collection” tab to create the collection. • Note: Make sure you already have monitoring templates for your targets.

41. Example

42. Template Collection Association • Click on “Associations” tab to associate TC with each node in hierarchy. • Note: All the targets which are members of the node as well as the targets in the sub-group will inherit the metrics of the templates involved. • Check for key-word “Valid Association” to verify the implementation.

43. Example

44. Find Un-Assigned Target • We can also check if we have some un-assigned targets left which are not being monitored by the standards defined via Administration Groups. • Click on “Associations” Tab. • Under “Actions” click on “UnassignedTargetsReports”

45. Example

46. Example

47. Synchronization Schedule • In case of Pending synchronization operations, the synchronization schedule comes into picture. • Pending Operations – like change in any monitoring template which is part of template collection. • So if there are any modification done to TC which is associated with any Administration Group, synchronization will occur.

48. Global Synchronization Schedule • How ? : Under Administration Groups. • Select “Association” tab and click “SynchronizationSchedule” • You can setup a schedule outside the peak hours. • PTR:- * The schedule interval is specified in days. * Synchronization will only occur if there are any pending operations.

49. Example

50. Example