When an Agent sends an Agent Event in VMX-Analysis, the event is encoded in a set of Capture Attributes.

The most important Attribute is Correlation ID, although this is not mandatory.

Attribute

Description

Correlation ID

If supplied, VMX-Analysis uses it to correlate all of the related Agent Events in a Flow. If empty, then VMX-Analysis will use an alternative strategy for correlation.

Agents also have a set of built-in Attributes, which are not editable but which can be used to aggregate data if required. These are:

Attribute

Description

Flow

A tag that represents a Flow within the monitored system; for example, 'ORDERS' for the order flow, as opposed to the ‘PRICE’ flow. An Agent is specific to a single flow. If one Visibility Point in an application sees multiple flows, each Flow must have its own Agent(s) at that point.

Subsystem

A tag that represents some sub-part of the application; for example, 'OM' for Order Manager.

Location

A tag that represents some geographical location where the monitored component within the application; for example, 'LONDON'.

Hostname

The physical host the related probe is running on, or for an external probe, the host being monitored.

ProcessId

The identifier of the process in which the probe is running.

Agents also have a set of custom Attributes, which are configured to meet requirement. Some examples:

Attribute

Description

probename

A name, such as “NasdaqDecoder“, that is assigned to the probe and which is passed to the Agent to put into this Attribute.

VLAN

A tag that provides information about the Virtual LAN.