Metric alert definitions operate on predefined sets of dimensions originating from the NAM Probe. 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 is available.
The name of the traffic analyzer. For more information see Concept of Protocol Analyzers on Dynatrace Community.
A universal container that can accommodate transactions.
Sites, areas, and regions define a logical grouping of clients and servers 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.
Sites, areas, and regions define a logical grouping of clients and servers 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.
Sites, areas, and regions define a logical grouping of clients and servers 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.
Is front-end tier?
Indicates whether a given tier is a front-end tier for a selected application.
A custom name created by a user for a selected link.
A link name, as reported by the information source (Network Monitoring Probe, Flow Collector, NAM Probe).
The type of a monitored link, for example Ethernet or Frame Relay.
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.
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 NAM Probe, based on referrer, timing relations between hits and per-transaction monitoring configured on the NAM Probe. 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 -- for example, server IP or server DNS -- has been used when formulating the query.
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 top n reported operations for a specific analyzer).
In this case, the number of operations and slow operations, as well as operation time and other transactional statistics, are 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 this case, only volumetric statistics (bytes, packets) are reported for this specific traffic.
DC RUM 2017 is the last version with official support for reporting groups.
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 NAM Server.
Server IP address
The IP address of the server.
The name of the system as it is listed in a DNS server.
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.
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 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 NAM Probe) 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.
A specific point of the application where we measure data. It can be a specific traffic type or a server.
The type of client traffic: real or synthetic, that is, generated by a synthetic agent.
A universal container that can accommodate operations. This metric refers only to transactions without errors.
Informs whether the transaction comes from Synthetic Monitoring probes, Agentless Monitoring Device, or is user-defined.