Using CA AppLogic › Appliance Developer Guide › Appliance Overview › Configure Appliance › Tie Boundary to Interior › Performance Counters

Performance Counters

Each appliance running the ccad (counter collection agent) daemon allows for custom counters to be defined and collected by third party utilities. This ability is a named extension interface and provides appliance creators with the option to monitor appliance-specific counter data through the standard MON user interface.

To monitor custom counters, add the counters definitions to the ccad configuration and feed the actual counter values to ccad. The custom counters have to be defined in an UDL format in the optional /etc/ccad.conf configuration file. When you make changes to the configuration, the ccad daemon must be restarted for the changes to take effect.

Here is a simple example configuration:

counters Apache
   {
   pace = 1000
   pipe = /tmp/cca
   counter Total_Accesses
      {
      name        = "Total hits"
      desc        = "Total number of hits"
      units       = "#"
      type        = "MAX"
      }
   counter Total_kBytes
      {
      name        = "Total bytes"
      desc        = "Total number of bytes"
      units       = "bytes"
      type        = "MAX"
      }
   counter BusyWorkers
      {
      name        = "Active requests"
      desc        = "Number of active requests"
      units       = "#"
      type        = "MAX"
      }
   counter IdleWorkers
      {
      name        = "Idle servers"
      desc        = "Number of idle servers"
      units       = "#"
      type        = "MAX"
      }
   }