The WebLogic Diagnostic Framework (WLDF) is an often overlooked feature of WebLogic which can be very powerful when configured properly.
If it’s so great, then why aren’t more people using it?
I can’t give a firm answer to that, but I suspect that the answer is likely because WLDF is so large, so comprehensive, and so terrifying to the uninitiated! There are a lot of concepts to get your head round before you can make good use of it, such that people frequently don’t bother. After all, where do you start with something so big?
In this blog, I hope to remedy that feeling a little, by pointing out some of the low-hanging fruit so you can get to know enough of the basics that you’ll be able to make use of some of the features, while having enough of a knowledge of the framework to take things further yourself.
What can I get out of it?
- Integration with JRockit Flight Recorder
- Diagnostic Image Capture
- a diagnostic snapshot for analysis of events
- event persistence
- diagnostic code which can be attached to applications or servers to track requests through the system
- captures metrics from runtime mbeans
- monitors the server and applications
- works with watches to provide other ways to read the data when a watch is triggered
- Monitoring dashboard
- a configurable view of data about WebLogic servers and applications in graph form
Aside from the complexity, the first thing you’ll notice is how unclear that diagram is to anyone who does not already have an understanding of WLDF and how to actually use it.
Our first topic? Very arbitrarily chosen: Watches
Check back next week!