Data Type | Description |
Dimension | A dimension represents data that you can categorize, query, and associate with a KPI (such as region or host name). Choose between an Existing Dimension or a New Dimension. Select Existing Dimension to link the event map to a dimension that already exists. Select the name of the existing dimension from the Dimension list, and select a value for the dimension in the Attribute list. Select New Dimension to link the event map to a dimension that does not yet exist. Enter a name for the dimension in the Dimension text box, and enter a value for the dimension in the Attribute text box. |
Transaction | A transaction is an attribute that you do not want to measure but that you would like to store in the database to use in a rule expression or to associate with a fact that arrives with the same event. Select the Transaction type to specify additional fields in a document, such as document identifiers, order numbers, or error messages. Optimize displays these fields on the KPI Instance Detail page and in alerts from rules defined for the event. To link the transaction data to a URL specified in an intelligent link (see
Defining Intelligent Links), select the name of the link from the Intelligent Link list, and select an optional parameter for the link from the Parameter list. Position the mouse pointer over a parameter name to display a description of the parameter. |
Measure | A measure (formerly known as a fact) is a measurable value (such as revenue or queue length) that the Analytic Engine can use for calculation or analysis. Select a calculation type and enter a unit of measure for the value: Calculation Type: Select Sum to total the data collected during the collection interval. Select Average to average the data collected during the collection interval. Select Last Value to use only the last data point collected. Select State to aggregate the binary state of the data point (such as online or offline). Select Count to count the data points during the collection interval. In the UOM text box, type a unit of measure (such as Dollars or Bytes). If you want the unit of measure to be automatically formatted when the KPI results are displayed, use one of the keywords described in the following step (keywords are not case sensitive). |
Date | Choose this data type to specify that the field is a date. Date fields are used for process deadlines (see
Deadline Standardized Error Types for more information). |
Unit of Measure Description | Keyword(s) for UOM Field | Display in KPI Results |
Dollars | “dollars” or “$” | <value to two decimals>$ |
Thousands of dollars | “$1000” Multiplies the result by 1000. | <value>,000.00 $ |
Percentage | “%” or “percent” Using “%” multiplies the result by 100. | <value to two decimals>% |
Size in bytes | bytes | <value to two decimals>bytes |
Size in kilobytes | k kbytes kilobytes | <value to two decimals>k |
Size in megabytes | mb megabytes | <value to two decimals>MB |
clients | clients | <value to one decimal> |
connection count | connection count | <value to one decimal> |
connections | connections | <value to one decimal> |
Item count | count | <value to one decimal> |
number of documents | documents | <value to one decimal> |
number of errors | errors | <value to one decimal> |
number of files | files | <value to one decimal> |
insert row count | insert row count | <value to one decimal> |
number of instances | instances | <value to one decimal> |
number of items | items | <value to one decimal> |
monitor count | monitor count | <value to one decimal> |
number of records | records | <value to one decimal> |
row count | row count | <value to one decimal> |
threads | threads | <value to one decimal> |
thread count | thread count | <value to one decimal> |
traces | traces | <value to one decimal> |
time in milliseconds | ms millis milliseconds | <hh:mm:ss> Hours <mm:ss> Minutes <ss:mm> Seconds <mmm> Milliseconds |
time in seconds | sec seconds | <hh:mm:ss> |
Online/offline | state | 0 = offline 1 = online |