0 
0 Read Time:2 Minute, 5 Second
Now Configuring Delegating Monitors to Use Dye Filtering:
Configure a dye mask and enable dye filtering for the HttpSessionDebug diagnostic monitor. In the Administration Console:
1. Select the application from the Deployments section, in our case the the FMW Â Welcome page application
2. Select Configuration–> Instrumentation, and click on the HttpSessionDebug monitor at the bottom of the page
3. Enable Dye filtering and select some Dye masks
4. Redeploy the application
In the EventArchivesData events should appear like:
Happy
0 %
Sad
0 %
Excited
0 %
Sleepy
0 %
Angry
0 %
Surprise
0 %
Related posts:
Another JDeveloper extension: Force Delete utility for ViewObjects (ADF Business Components pka BC4J) 
Providing default-values for find-pages in JHeadstart applications (UIX/BC4J/Struts) Installing Tomcat5.5 and integrating it with Apache 1.3 Book review: Business Process Execution Language Use Data Tree in List of Values Window – ADF BC and UIX and JHeadstartPages: 1 2
Great post. Instrumentation can also be used to get a detailed overview of requests performance, and how much time is spent in each application component:
http://oraclemiddleware.wordpress.com/2012/02/01/instrumenting-weblogic-applications-with-wldf-where-does-the-application-spend-time/
Hi Michel,
I cannot see the picture. It seems that the link is not correct.
Thanks: now I can see the picture after all.
Lucas
Hi Lucas
I added an example. Normally, when you instrument your application with monitors it appears in EventsArchiveData, unless configured properly.
kind regards
Â
Michel
Hi Michel,
Thanks for an interesting new piece of information. I was wondering: can you add a screenshot that demonstrates what the logging would look like that you gather for a specific session, user or IP adress?
kind regards,
Lucas