As a business object progresses across the network or through an application, its data is captured by probes and passed to Agents. Agents at different points in the business object’s journey may receive different or additional data about the business object, which are mapped to Attributes. When the data is passed to VMX-Analysis, it puts it all together to create an Item History for that business object.

Item History
All captured data about a business object, the probe ID, and time the probe saw the item.


The Item History includes:

  • its primary or correlation id or alternative identifiers.

  • any other identifiers the item is known by, for example a subsystem or exchange-specific id.

  • the union of capture attributes from the various probes that have seen the item.

  • the probes that have seen the item and the time at which it was seen.

How are Item Histories used?

Item histories can be used to query the state of a given business item and its transit through a monitored system. VMX-Explorer provides an Item Trace view in which you’ll select specific business items by id or time window. You can then drill down to individual hops that specific item made along the way.

To maximise performance, Item Histories are stored in the Beeks Analytics data cache. They can be exported to a persistent database for offline reporting if needed. Beeks Analytics allows full control of how the Item History is mapped to a relational database format and which Agent points in the item's transit are persisted. For optimal efficiency, items should be persisted at the end point of their normal transit.