Metrics is data that is gathered from an agent. Typically, an agent is an application server, such as:

• a JBoss application server
• a Tomcat application server
• a WebSphere application server

For example, some possible metrics are:

• the agents memory usage
• the agents CPU utlization
• the agents garbage collection

Agents and the Enterprise Manager

On each server that contains agents, the /opt/wily/Introscope/core/config/IntroscopeAgent.profile file contains the configuration for all of the agents on the server. In the IntroscopeAgent.profile file, the hostname and port of the Enterprise Manager will be defined. The Enterprise Manager contains a central repository of the metrics from each agent.

introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=your_hostname
introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=your_port

Old Metrics (aging)

By default, metric aging is turned on. Setting this property to "false" or removing this property from the IntroscopeAgent.profile file will disable metric aging.

introscope.agent.metricAging.turnOn=true

The heartbeat interval defines how many seconds elapse between polling for metrics that have aged.

introscope.agent.metricAging.heartbeatInterval=86400

Number of time slices is the amount of time, in seconds, that has elapsed after a metric was last reported. Number of time slices is used in conjunction with other metric aging configurations to determine when a metric is eligible to be aged out.

introscope.agent.metricAging.numberTimeslices=180000

Logs

In the IntroscopeAgent.profile file, there are two main agent log files, autoprobe.log and IntroscopeAgent.log.

introscope.autoprobe.logfile=/path/to/autoprobe.log

log4j.appender.logfile.File=/path/to/IntroscopeAgent.log