1. Middleware Monitoring Using Dynatrace Plugins By Todd Ellis IT Manager, Omnicare February 25, 2015

2. Monitoring Philosophy

3. Dashboards and Troubleshooting Email Alerts Central Dashboard for NOC or Administrator Integration into Service Now

4. Dashboard Design

5. Dashboard Overview

6. Key Health Metrics Captured Through JMX

7. JMS Overview

8. Weblogic Thread Overview

9. What Can We Monitor? JMV Threads Clusters Transactions File Stores JMS SAF Message Bridges Application Data/States EJB JDBC Server State/Health

10. Metrics to become Pro-Active instead of Re-Active JVM Execute Threads Workmanagers JDBC Applications JMS Server Running Time Monitoring Time

11. JVM GC Time

12. Execute Thread Counts

13. Workmanager Thread Usage

14. JDBC

15. Application Health Applications Deployed

16. JMS Oldest Message Age

17. Server Running Time

18. Monitoring Time

19. Root Cause Analysis User called and reported abnormal slowness in the application. User confirmed system went back to normal after a few minutes.

20. Dynatrace Monitoring Value of Dynatrace & Plugins to Omnicare: Help Desk was able to assure the customer that IT noticed the issue and was working to resolve and/or prevent the performance issue in the future. Weblogic and JVM monitoring reported multiple issues prior to the user calling and complaining of system performance issue.

21. Threads

22. JDBC

23. Application Data

24. Application That Was in Use

25. JVM Root Cause

26. Q&A Questions? For more information specifically about the plugin check out my Weblogic Monitoring and JVM JXM Monitoring Plugin on the Dynatrace Community. My contact: Todd Ellis, tellis04901@yahoo.comtellis04901@yahoo.com