SungHoon_Kim

How to get Web Agent Cache Utilization and other statistics information

Blog Post created by SungHoon_Kim Employee on Jan 12, 2016

Title:

        - Web Agent does not log its cache utilization nor how many authentications it has performed in its log files, then how can you check the statistics?

 

Description:

In order to get the cache utilization and other statistics you will need to setup OneView monitor.

OneView monitor will give you the list of Web Agent and you get the statistics from there.

Or, Wily Instroscope would give you even more details with user friendly views.

But even when you don't have those configured, you can still get the statistics.

Out of the box, your Web Agent is configured to send its statistics to the Policy Server for One View Monitor.

In the Policy Server trace log(smtracedefault.log) you will find <SMMON:***> entries which is a statistics report from that Web Agent.

        By capturing the SMMON data that is sent by Web Agent, we get access to the statistics information of that particular Web Agent.

 

Instructions:

- Step1: Ensure that your Agent Configuration Object has (enablemonitoring='yes') and webagent.log shows the same.

     * This tells Web Agent to send the SMMON data to Policy Server

- Step2: Check which Policy Server this agent will be connecting to and send SMMON data every 30 seconds.

     * webagent.log will show if you are running in failover mode(enablefailover='yes') and which policy server it is connecting to (policyserver='192.168.1.100,44441,44442,44443).

- Step3: Setup Policy Server profiler to log the SMMON data. Minimum requirement is as below 2 lines for components and data.

     * components: Loogin_Logout/Receive_Request

     * date: Date, Time, AgentName, Data

     * Optionally you can filter only the SMMON data by adding "Data: @@SMMON" in a separate line.

     Sample smtracedefault.txt file below.

  

Sample "<PS>/config/smtracedefault.txt" file with filter to log only "SMMON" data. (5th line is empty line)

components: Login_Logout/Receive_Request

data: Date, Time, AgentName, Data

version: 1.1

Data: @@SMMON

 

It should generate smtracedefault.log as below.

The [AgentName] section shows the TrustedHost name where this message is coming from.

The [Data] section has the SMMON data and you need to check the "AgentName" within the SMMON data in order to understand which agent statistics it is for because you may have multiple agents sharing the same SmHost.conf file.

 

     - Step4: Now that you have SMMON data, you need to extract the information.

          * It will be easier to view each entry if you  have some sort of XML parser.

SMMON data sample

<SMMON:ComponentRegistered xmlns:SMMON='http://netegrity.com/monitor'>

    <Host HostId='192.168.201.105'>

        <SmComponent CompPath='Agent;6128'></SmComponent>

    </Host>

</SMMON:ComponentRegistered>

<SMMON:ComponentData xmlns:SMMON='http://netegrity.com/monitor'>

    <Host HostId='192.168.201.105'>

        <SmComponent CompPath='Agent;6128' Version='12.52QMR01'>

            <Name>agent.iis</Name>

            <Info>Product=WebAgent,Platform=IIS75/Windows,Version=12.52QMR01,Update=HF03,Label=767,FileVersion=12.52.0103.767,UTC=1452575359,TZ=-10,Crypto=128</Info>

            <ResourceCacheHits>14</ResourceCacheHits>

            <ResourceCacheMisses>5</ResourceCacheMisses>

            <UserSessionCacheHits>1</UserSessionCacheHits>

            <UserSessionCacheMisses>3</UserSessionCacheMisses>

            <IsProtectedCount>5</IsProtectedCount>

            <IsProtectedErrors>0</IsProtectedErrors>

            <LoginCount>3</LoginCount>

            <LoginErrors>0</LoginErrors>

            <LoginFailures>0</LoginFailures>

            <ValidationCount>0</ValidationCount>

            <ValidationErrors>0</ValidationErrors>

            <ValidationFailures>0</ValidationFailures>

            <AuthorizeCount>4</AuthorizeCount>

            <AuthorizeErrors>0</AuthorizeErrors>

            <AuthorizeFailures>0</AuthorizeFailures>

            <CrosssiteScriptHits>0</CrosssiteScriptHits>

            <BadURLCharsHits>0</BadURLCharsHits>

            <BadCookieHitsCount>0</BadCookieHitsCount>

            <ExpiredCookieHitsCount>0</ExpiredCookieHitsCount>

            <IsProtectedAvgTime>1</IsProtectedAvgTime>

            <LoginAvgTime>270</LoginAvgTime>

            <ValidationAvgTime>0</ValidationAvgTime>

            <AuthorizeAvgTime>1</AuthorizeAvgTime>

            <ResourceCacheCount>5</ResourceCacheCount>

            <UserSessionCacheCount>3</UserSessionCacheCount>

            <ResourceCacheMax>1000</ResourceCacheMax>

            <UserSessionCacheMax>1000</UserSessionCacheMax>

        </SmComponent>

    </Host>

</SMMON:ComponentData>

          * The important part of the data above is "HostId", "Name" and the rest of the statstics information in the "SmComponent" section.

 

Additional Information:

- This is part of Web Agent Core feature so all regular Web Agents will generate and send this SMMON data to policy server regardless of platform or version.

 

** This article is now published as a Knowledge Document linked below.

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1479852.aspx

Outcomes