Troubleshooting Web Agent(s) and Policy Server(s) communication issues which requires additional logging information in the trace logs.
The default Web Agent traces does not provide enough information to determine the reason why a Web Agent chooses one Policy Server or another in the Cluster or which PolicyServer has connectivity problem.
Web Agent: 12.52.x
Enable the Agent_Con_Manager component in the Web Agent traces to obtain the connection information. To do this, follow the steps below:
components: AgentFramework, HTTPAgent, WebAgent
data: Date, Time, Pid, Tid, SrcFile, Function, TransactionID, IPAddr, IPPort, AgentName, Resource, User, Message
components: AgentFramework, HTTPAgent, WebAgent, AgentFunc, Agent_Con_Manager
data: Date, Time, PreciseTime, Pid, Tid, TransactionID, Message, SrcFile, Function, RequestIPAddr, IPAddr, IPPort, AgentName, Domain, DomainOID, Realm, RealmOID, Resource, Action, User, SessionSpec, SessionID, CertSerial, SubjectDN, IssuerDN, UserDN, Threshold, Throughput, MinThroughput, MaxThroughput, HandleCount, BusyHandleCount, FreeHandleCount, State, ClusterID
Additional information in the traces will be generated to help troubleshoot the issues.
Note that above additional components come from 2 other config templates located in the same directory of WebAgentTrace.conf.
AgentConMgr.conf
AgentFunctions.conf