Developer Partner Community

  • May 16, 2014

Getting the most out of WLDF Part 2: Watches by C2B2

Juergen Kress
PaaS Partner Adoption

In this post, I'll be looking at using watches in WLDF.
What is a watch? A watch, at its most basic, is simply a way to monitor one of three things:

  • MBeans
  • A server log
  • Instrumentation (event) data

To configure an instrumentation watch, you first need to know what instrumentation is, and how to instrument applications or servers, so we’ll put that to one side for now. A server log watch is exactly that - a watch to monitor the server log for anything you want! For example, all Critical severity log entries, entries which mention a particular server or particular log message IDs. An MBean watch relies on the Harvester to collect server runtime MBean metrics which does not need to be configured separately for your watch to work, but do bear in mind that the data gathered will not be archived unless you configure the Harvester properly:

If you define a watch rule to monitor an MBean (or MBean attributes) that the Harvester is not configured to harvest, the watch will work. The Harvester will "implicitly" harvest values to satisfy the requirements set in the defined watch rules. However, data harvested in this way (that is, implicitly for a watch) will not be archived. See Chapter 7, "Configuring the Harvester for Metric Collection," for more information about the Harvester.

How do I make a watch? I’ve already mentioned that Instrumentation watches require a little understanding of instrumentation first, so I won’t cover them here. If you’re already familiar with instrumentation, then configuring watches for your instrumented applications isn’t too tricky.

Step 1: Create a Diagnostic Module The first step in creating watches is always the same. In the Domain Structure pane, select “Diagnostic Modules” under the “Diagnostics” entry.

Select a diagnostic module if you’ve created one, or create a new one if not. Since creating a new module only requires you to name it (and provide an optional description), you’ll need to configure it once you’ve created it. The most important thing to do is to target it to the server you want to monitor. Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.