VMX-Analysis can use cross reference beacons to correlate Agent Events where an Alt ID is available at a given probe point but there is no natural means of mapping this to the Correlation id from other points in the flow.

Cross reference beacon
Cross reference beacons transmit two identifiers that VMX-Analysis uses to form a cross reference, plus a Set ID that categorises cross reference beacons by purpose.

How are cross reference beacons created when we cannot link a Correlation ID with an Alt ID?
When there is no Correlation ID and Alt ID at an Agent point, we can create a cross reference beacon using information from a source that sits outside the business flow, such as database or feed. In this case, we instantiate a cross reference probe, which is a probe that has an API to the external source. We then request a cross reference beacon from the source via the API and this provides the 2 identifiers that make up the cross reference. The Agent ID provides a unique set identifier for the cross reference beacon.

Cross reference beacons are also known as correlation beacons.

Example

A message at probe X contains a systemX identifier (systemXid) but not the correlation ID. No messages include both the systemXid and correlation ID so we can’t link the two identifiers.

An independent system knows how systemXid maps to the Correlation ID captured at other points in the Flow. A cross reference beacon injects the cross references for systemXid and the corresponding correlationid. 

The system is configured to use a cross-reference correlation strategy for the Agent point at that probe. The configured cross reference beacon then correlates Agent Events from that point.