A fairly unknown tool within WLDF(WebLogic Diagnostic Framework) is the DyeInjection Monitor. With this monitor configured one can track a  user or client address within a WebLogic system.
You can configure WLDF to check for  every request that enters the system and add a unique ID within a context to track this request in it’s flow.A diagnostic context contains a unique context ID and a dye vector, which identifies characteristics of the context.
First of all you will have to create a diagnostic module configured to use the DyeInjection Monitor:
1. Create a Diagnostic Module within your WebLogic Admin Console
2. Add the DyeInjection Monitor to the Module, from the tab instrumentation, and add the DyeInjection Monitor
3. Within the DyeInjection Monitor, you can configure the originatin IP Adress and user. ( you can not use DNS for it)
The following flags should be used:
ADDRn –> Originating IP adress
USERn –> Specific User or client name
COOKIEn –>are set in the diagnostic context for an HTTP request, if the request contains the cookie named weblogic.diagnostics.dye and its value is equal to the value of the respective property of the DyeInjection monitor.
CONNECTORn –>These dye flags are set by the connector drivers to identify request properties specific to their situations ( for instance a JDBC connector)
Other ones are: THROTTLE, PROTOCOL_HTTP,PROTOCOL_SOAP, PROTOCOL_IIOP, PROTOCOL_RMI, PROTOCOL_SSL, PROTOCOL_T3. These are are set implicitly by WLDF.
4 Configure a dye mask and enable dye filtering for the for an already instrumented application diagnostic monitor.
Here’s the way how to instrument an application with Diagnostics:
– In the Admin Console, click Deployments
– On the Summary of Deployments > Control page, click the name of the application or application module for which you want to configure diagnostic monitors. I use the FMW  Welcome page application inhere, just as an example
– Select Configuration > Instrumentation. and add a Monitor from Library, and then select the options you’d like to attach
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