13.4 Viewing Statistics Using the CLI

By using the CLI, you can view statistics for one or all instances of a configuration, for a specific virtual server, for a specific origin-server pool, and for a specific TCP proxy.

Note:

The CLI examples in this section are shown in shell mode (tadm>). For information about invoking the CLI shell, see Section 2.3.1, "Accessing the Command-Line Interface."

• To view statistics for one or all instances of a configuration, run the get-config-stats command, as shown in the following example:

  tadm> get-config-stats --config=soa
  countRequests=20
  rpsLast1MinAvg=0.06666667
  rpsLast5MinAvg=0.013377926
  rpsLast15MinAvg=0.0022099447
  countErrors=2
  epsLast1MinAvg=0.0
  epsLast5MinAvg=0.0
  epsLast15MinAvg=0.0
  maxResponseTime=23.001
  rtLast1MinAvg=1.0
  rtLast5MinAvg=1.0
  rtLast15MinAvg=1.0
  

  To view statistics for a specific instance of a configuration, run the get-config-stats command with the --node option.

• To view aggregated virtual-server statistics for one or all instances of a configuration, run the get-virtual-server-stats command, as shown in the following example:

  tadm> get-virtual-server-stats --config=soa --vs=vs1
  count200=9
  count2xx=9
  count302=0
  count304=6
  count3xx=6
  count400=0
  count401=0
  count403=0
  count404=4
  count4xx=4
  count503=0
  count5xx=2
  countBytesReceived=42215
  countBytesTransmitted=69298
  countErrors=2
  countOpenConnections=0
  countOther=0
  countRequests=21
  rateBytesTransmitted=0
  vsName=vs1
  webapp-firewall.countRequestsAllowed=5
  webapp-firewall.countRequestsDenied=2
  webapp-firewall.countRequestsDenyDetected=0
  webapp-firewall.countRequestsDropDetected=0
  webapp-firewall.countRequestsDropped=1
  webapp-firewall.countRequestsIntercepted=10
  webapp-firewall.countRequestsRedirectDetected=0
  webapp-firewall.countRequestsRedirected=2
  websocket.countActiveConnections=1
  websocket.countBytesReceived=500
  websocket.countBytesTransmitted=200
  websocket.countRequestsAborted=0
  websocket.countRequestsTimedout=0
  websocket.countUpgradeRequests=1
  websocket.countUpgradeRequestsFailed=0
  websocket.countUpgradeRequestsRejected=1
  websocket.millisecondsConnectionActiveAverage=1000
  

  To view virtual-server statistics for a specific instance of a configuration, run the get-virtual-server-stats command with the --node option.

• To view statistics for a specific origin-server pool, run the get-origin-server-stats command, as shown in the following example:

  tadm> get-origin-server-stats --config=soa --node=soa.example.com --origin-server-pool=wls1
  origin-server.1.backup=0
  origin-server.1.countActiveConnections=0
  origin-server.1.countBytesReceived=11776
  origin-server.1.countBytesTransmitted=15024
  origin-server.1.countConnectAttempts=41
  origin-server.1.countConnectFailures=0
  origin-server.1.countIdleConnections=1
  origin-server.1.countMarkedOffline=0
  origin-server.1.countRequests=44
  origin-server.1.countRequestsAborted=0
  origin-server.1.countRequestsTimedout=0
  origin-server.1.discovered=0
  origin-server.1.name=soa-app.example.com:1900
  origin-server.1.online=1
  origin-server.1.rampedUp=1
  origin-server.1.secondsOnline=20
  origin-server.1.type=http
  origin-server.1.websocket.countRequests=2
  origin-server.1.websocket.countUpgradeRejectedRequests=1
  origin-server.1.websocket.countFailedStrictRequests=1
  origin-server.1.websocket.countUpgradedRequests=1
  origin-server.1.websocket.countAbortedRequests=0
  origin-server.1.websocket.countTimeoutRequests=0
  origin-server.1.websocket.countBytesReceived=500
  origin-server.1.websocket.countBytesTransmitted=200
  origin-server.1.websocket.countActiveConnections=1
  origin-server.1.websocket.millisecondsConnectionActiveAverage=1000
  ...and so on for each of the origin servers in the specified pool
  

• To view detailed statistics for an instance in XML format, run the get-stats-xml command, as shown in the following example:

  tadm> get-stats-xml --config=soa --node=soa.example.com
  

  For a sample of the report, see Section 13.7.

• To view a summary of the statistics for an instance in plain-text format, run the get-perfdump command, as shown in the following example:

  tadm> get-perfdump --config=soa --node=soa.example.com
  

  For a sample of the report, see Section 13.8.

• To view statistics for a TCP proxy, run the get-tcp-proxy-stats command, as shown in the following example:

  tadm> get-tcp-proxy-stats --config=soa --tcp-proxy=tcp_proxy1
  interfaces:*:9898
  countActiveConnections=3
  countRequests=10
  countRequestsAborted=2
  countRequestsTimeout=4
  countBytesReceived=400
  countBytesTransmitted=200
  milliSecondsConnectionActiveAverage=1600
  mode=1
  name=tcp-proxy-1
  

For more information about the CLI commands mentioned in this section, see the Oracle Traffic Director Command-Line Reference or run the commands with the --help option.

13.4.1 Automating Retrieval of Monitoring Statistics

Oracle Traffic Director allows you to continuously retrieve monitoring statistics in an automated manner using a cron job. To enable automated collection of statistics:

Create a file such as .tadmrc within the Oracle Traffic Director admin user home directory:

cat > ~/.tadmrc
set tadm_password  <
[ CTRL-D ] 

The administrator can continuously collect Oracle Traffic Director monitoring statistics every 5 minutes through a cron job, for example:

<otd-install-root>/bin/tadm get-perfdump —user=.. —config=..   —node=..  >>  <output-file>