ITCAM for Transactions WRT agent tips,best practices,pitfalls (part2)
ericmtn 1000009W88 Comment (1) Visits (7670)
1) WRT does not report in TEP, under the "Transactions" view, an expected Transaction that is defined with some Filters configured in AMC configuration editor settings.
Filters defined to report this transaction, under the Filter tab :
URLHostName = <host>
URLPath = <path>
URLFile = <file>
Expected good results as below, where the transaction "IBT_BA_Watchlist" appears in TEP. But BY DEFAULT, it doesn't appear. Why?
You would need to take a network capture or trace of your http traffic, using Wireshark, Fiddler, etc.. tool and review the content of the traffic involved, when you are manually accessing with a web browser the targeted transaction.
Here is the example of http://<host>/<url path
If you apply a filter inside Wirehark, like example below: http contains "/watchlist" and press the blue arrow on the right hand side of this bar,
and then look at the packets associated to the Transaction that you want to monitor, you may notice in the HTTP packet details that there is no referer info:
In comparison, here is another Transaction that was monitored and returned just fine, BY DEFAULT, with WRT, because it contains a referer info:
If you look on the WRT agent machine in the kfcm120/ kfcmserver log, file you may also notice lines like :
ORIGIN OF THIS SYMPTOM:
[ For kfcmenv file location, see :
So we can set for example
The configuration variable "KFC
The variable :
has to be used with caution. it may cause high impact on performance of WRT agent, including possible core of kfcm120 program for example, depending on the load and amount of traffic involved with your WRT environment.
So better, less intrusive setting potentially is to use
variable, like :
you can also refer to this other blog that covers similar subject :
PART 3 of this BLOG:
Subscribe and follow us for all the latest information directly on your social feeds: