ITCAM4Tx Tracking : WRT in Agent-Based versus AgentLess
ericmtn 1000009W88 Visits (2670)
1. The two ways to integrate the RT WRT agent with Tx Tracking agents are :
Agent-based and AgentLess.
workspaces in TEP.
configuration. It will cause the WRT (t5) agent to fill its 'T5TCPSTAT' attribute group workspaces.
The Tx Reporter (to) agent will then need to be configured to read this data, using its
"Aggregation Agent List" ; but by default it is configured to read all tu and t5 agents.
in TEP will all be empty. You can turn none, either or both on.
selected. So having it disabled when HTTP(S) tracking is not enabled is by design.
You can refer to articles available in IBM Knowledge Centre
see kincinfo -t command results:
it shows here that WRT (t5) version 188.8.131.52 and Tx Reporter (to) version 184.108.40.206 (7.4 + IF1) are installed on a
The 'Monitor All TCP traffic' option is selected/ needed for Agentless mode.
The 'Monitor remote network traffic' option is selected/needed for Agentless mode
You can leave the 'Aggregation Agent List' field blank. The Reporter will then collect data from all
in TEP, WRT agent details workspace info should match what you have setup during configuration of the
WRT 'Network' workspace should contain data. Latency Time and Average Response Time views will also
report data, provided you have enabled History Collection configuration for T5TCPSTAT attribute group,
as seen further below.
WRT T5TCPSTAT attribute group Basic setting example
NS180:T5 here, where WRT agent is installed and running.
If all is configured and work properly, you should see this kind of results in TEP
Tx Reporter Status view:
If If you have for instance 2 WRT agents configured in agentless mode and installed in your environment,
the field 'aggregation Agent contacts available' field of Reporter Status view should report the right number
of agentless agents.
In my test environment, I had 2 WRT agent in agentless, hence the value of "2" in 'aggregation Agent
contacts available' column.
Tx Reporter -> Workspace -> 'Tx Reporter Agent Diagnostics' should display as seen above messages
showing evidence of data being collected by the Tx reporter agent from its aggregation agents.
Tx Reporter -> Workspace -> Agentless Data should report data in Network Topology view