Data Monitoring Using CA Application Performance Management

If you are already using CA Application Performance Management (CA APM) in your organization, you can use CA APM to monitor the following statistics of a Tomcat server and monitor the health of smsps:
casso127
If you are already using CA Application Performance Management (CA APM) in your organization, you can use CA APM to monitor the following statistics of a Tomcat server and monitor the health of 
CA Access Gateway
:
  • The average response time of each of the following
    CA Access Gateway
     components:
    • Session Discovery
    • Java Web Agent
    • Post Agent Session Writer
    • Proxy Rules Filter
    • Noodle Servlet
    • HTTP Client
  • The average response time of each backend server
  • The
    CA Access Gateway
     request wait time
  • Number of hits for each proxy rule
  • The
    CA Access Gateway
     Agent framework instances health data
The data monitoring section has the following format:
<Server>
.
.
monitor_data_buffer_size="1000"
.
.
</Server>
<metric-reporter name="CA APM Metric Reporter"> 
enabled="yes"
class="com.ca.proxy.monitor.wily.WilyMetricReporter"
endpoint="tcp://localhost:8886"
</metric-reporter>
monitor_data_buffer_size
Specifies the size of the buffer the 
CA Access Gateway
maintains to store the collected statistics before sending them/statistics to CA APM.
Default
: 1000
metric-reporter name
Specifies the name of the metric reporter. You can use this name to debug any metric errors.
enabled
Specifies the state of the data monitoring feature. If you want to monitor the health of SPS, set the value to yes. If you do not want to monitor the health of the SPS, set the value to no.
Default
: no
endpoint
Specifies the configuration details of the EPAgent. Start the EPAgent before you communicate with the SPS. The endpoint parameter has the following format:
protocol
://
hostname_of_EPAgent
:
port
protocol
Specifies the communication protocol that the EPAgent uses.
hostname_EPAgent
Specifies the hostname of the machine where the EPAgent is installed.
Default
: localhost
port
Specifies the port number the EPAgent uses to communicate with
CA Access Gateway
. If you use TCP protocol, enter the network data port that is configured in EPAgent. If you use HTTP protocol, enter the HTTP port number that is configured in EPAgent.
Enable Data Monitoring
Perform the following steps to enable data monitoring:
Note
: For information about configuring, see CA Application Performance Management documentation.
  1. Configure CA APM to collect metrics from
    CA Access Gateway
    .
  2. Configure the server.conf file by performing the following steps:
    1. Open the server.conf file and navigate to the metric-reporter section.
    2. Set the following value:
      enabled=yes
    3. (Optional) To monitor the agent instance metrics configured with
      CA Access Gateway
      , set the following value:
      enablemonitoring=yes
    4. Save the changes.
  3. Configure the ACO for each Web Agent that is configured with
    CA Access Gateway
    .
  4. Start CA APM.
  5. Restart
    CA Access Gateway
    .
Monitor Web Agents with OneView Monitor
OneView Monitor reports cache statistics and other information to Policy Server, which administrators can use to analyze and fine-tune the Web Agent. You control OneView monitor with the following parameter:
EnableMonitoring
Specifies whether the agent sends monitoring information to Policy Server.
Default
: Yes