MiddlewareMonitoring Using Dynatrace Plugins

By Todd EllisIT Manager, Omnicare

February 25, 2015

Monitoring Philosophy

Dashboards and Troubleshooting

• Email Alerts

• Central Dashboard for NOC or Administrator

• Integration into Service Now

Dashboard Design

Dashboard Overview

Key Health Metrics Captured Through JMX

JMS Overview

Weblogic Thread Overview

What Can We Monitor?

• JMV• Threads• Clusters• Transactions• File Stores• JMS• SAF• Message Bridges• Application Data/States• EJB• JDBC• Server State/Health

Metrics to become Pro-Active instead of Re-Active

• JVM• Execute Threads• Workmanagers• JDBC• Applications• JMS• Server Running Time• Monitoring Time

JVM GC Time

Execute Thread Counts

Workmanager Thread Usage

JDBC

Application Health Applications Deployed

JMS Oldest Message Age

Server Running Time

Monitoring Time

Root Cause Analysis

• User called and reported abnormal slowness in the application.

• User confirmed system went back to normal after a few minutes.

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.

Threads

JDBC

Application Data

Application That Was in Use

JVM Root Cause

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.com