There is a file named EPAgent8.x.x.xGuide.pdf and it states the following:
XML format for metric data
Where the “simple” format limits the Introscope metric types, XML style format
allows the plug-in to report additional information, such as Introscope metric
name, Introscope metric type, and value, as in the following example:
<metric type="LongCounter" name="Resource Usage|File IO:diskWrites"
value="37" />
<metric type="StringEvent" name="Apache Errors:LastErrorString"
value="ERROR: Apache shutdown unexpectedly" />
XML format guidelines:
This allows full support of Introscope data types as well as equals signs in both
metric names and values.
The “type” attribute of a metric must be one of the following:
- PerIntervalCounter—the value is a rate "per interval" where the interval can
change. These metrics are aggregated over time by summing the values.
For example, if there were 10 method invocations per 15 seconds followed
by 15 method invocations per 15 seconds, then aggregating to 30 seconds
would result in "25 method invocations per 30 seconds".
- IntCounter—int values can go up and down
- IntAverage—int value that is averaged over time
- IntRate—the value is a per second rate. These metrics are aggregated over
time by taking the average of the values.
- LongCounter—long values can go up and down
-LongAverage—long value that is averaged over time
- StringEvent—represents a type which periodically generates Strings. This
recorder does not have a notion of current value; it merely reports events
in the order in which they are reported to it.
- Timestamp—a type which generates successively increasing timestamps.
The comparison is case-insensitive (to make it easy for the plug-in writer). If
a numeric type is supplied, but the value is non-numeric, nothing is reported
to Introscope and an error will be logged by the EPAgent.
Is this what you are looking for?