Metric alert definitions operate on pre-defined sets of dimensions originating from the AMD. This list contains dimensions that you can use when configuring detector settings for new metric alert definitions. Note, however, that for each alert category—basic, EUE data, Citrix data or Point-to-Point data—a different set of dimensions will be available.
Analyzer
The name of the traffic analyzer. For more information see Concept of Protocol Analyzers
Application
A universal container that can accommodate transactions. Client area
Sites, areas, and regions define a logical grouping of clients and servers, or Backbobne nodes in case of Synthetic Backbone reports, into a hierarchy. They are based on manual definitions and/or on clients' BGP Autonomous System names, CIDR blocks or subnets. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.
Client region
Sites, areas, and regions define a logical grouping of clients and servers, or Backbone nodes in case of Synthetic Backbone reports, into a hierarchy. They are based on manual definitions and/or on clients' BGP Autonomous System names. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.
Client site
Sites, areas, and regions define a logical grouping of clients and servers, or Backbobne nodes in case of Synthetic Backbone reports, into a hierarchy. They are based on manual definitions, clients' BGP Autonomous System names, CIDR blocks or subnets. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.
Client site UDL
A dimension designed to filter only the User Defined Links. By default it is set to true (Yes) for WAN Optimization Sites report.
Client site WAN Optimized Link
Indicates whether a site to which the client belongs is selected as both a UDL and a WAN optimized link.
Internal traffic handling
Indicates if the traffic within a site should be monitored or not. Used for filtering traffic when you define an internetwork alert.
Is front-end tier?
Indicates whether a given tier is a front-end tier for a selected application. Link alias
A custom name created by a user for a selected link. Link name
A link name, as reported by the information source (Network Monitoring Probe, Flow Collector, AMD).
Link type
The type of a monitored link, for example Ethernet or Frame Relay. Module
Module is the third level in the reporting hierarchy. For example, in database monitoring this is the database name, and in SOAP monitoring this is the SOAP service. This entity can be broken to smaller bits such as tasks.
Operation
For HTTP, this is the URL of the base page to which the hit belongs. For other analyzers this can be a query, operation type or an operation status. Operation is ascertained by the AMD, based on referrer, timing relations between hits and per-transaction monitoring configured on the AMD. This dimension can assume values of a particular operation - if this operation is monitored. Note: The visibility of this dimension on reports depends on whether another dimension, related to servers - e.g. server IP or server DNS - has been used when formulating the query.
The All other operations record serves a catch-all net for al the traffic that has been seen to-from a server, but was not classified as belonging to a specific monitored-by-name operation. It accounts for statistics of:
• operations which were not reported in per specific operation records (for example those that fall out of topN reported operations for a specific analyzer) - in such case the number of operations and slow operations, as well as operation time and other transactional statistics will be reported as an aggregate/average;
• traffic which was not classified to any operations (for example, idle TCP session closure, TCP handshake without any operation, etc) - in such case only volumetric statistics (bytes, packets) will be reported for this specific traffic.
Reporting group (obsolete)
Reporting group is a universal container that can accommodate software services, servers, URLs or any combination of these. Reporting groups can contain software services of every type. Advanced Diagnostics Server can import reporting group configuration from Central Analysis Server.
Server IP address
The IP address of the server.
Server name
The name of the server resolved by a DNS server. Service
Service is the highest level of multi-level reporting hierarchy. For example, in SAP GUI monitoring this is the business process. This entity can be broken to smaller bits such as modules.
Software service
The software service name, where by a software service we understand a service implemented by a specific piece of software, offered on a TCP or UDP port of one or more servers and identified by a particular TCP port number.
Task (obsolete)
Task is the second level in the reporting hierarchy. For example, in HTTP monitoring this is the page name; in database monitoring this is the operation name (may contain regular expression if configured on the AMD) or operation type prefix, and in SOAP monitoring this is the SOAP method. This entity can be broken to smaller bits such as operations or operation types.
Tier
A specific point of the application where we measure data. It can be a specific traffic type or a server.
Traffic type
The type of client traffic: real or synthetic, that is, generated by a synthetic agent. Transaction
A universal container that can accommodate operations. This metric refers only to transactions without errors.
Transaction source
Informs whether the transaction comes from Synthetic Monitoring probes, Agentless Monitoring Device, Cerner RTMS, or is user-defined.
WAN link name
The name of the WAN link.
stepName - ### !!! FIXME Name missing in TMX !!! - internalId: stepName - descriptionTmxId: RTM_DV_CVENT_HELP_DIMENSION_stepName
An operation-task pair attribute or an (ordered) alias for operation occurrences. Step names are assigned in a configuration file read by the report server or come from third-party sources.
Within a given task, steps enable you to distinguish operations by name. Because steps are assigned sequence numbers, you can follow the order of operations recorded for a given task.
Each step is always related to one operation and one task. It is possible, however, for several operations to have identical step names and each task to have more than one step, so that many-to-one relationships are likely to occur on reports.