Passive Event Process Monitoring

Scenario ID¶

Siphoning off messages or meta-data from all key flows to monitor an overall event transaction process

A typical scenario is where an order or business transaction is not fully orchestrated through a fulfillment process, so that correlation of events down the chain is difficult or manual.
All messages (or their meta-data) are routed both to target and towards a central monitoring system that logs at least the header or other key fields required to link the events together.
The monitoring system does not affect the process, but can raise alarms and allow e.g. a service desk to see how far the process has run and where it may have stopped or failed.
The pattern is seen mandatory for the governance model and it will be implemented using a common message header (CMH).
If there is no CMH, then the monitoring platform needs to know how to read out the key meta-data information from within all specific messages.
i.e. for the areas where monitoring is needed, all the interfaces must be provided with a CMH, and all messages should be siphoned off to a monitoring system.

Implement this pattern within flows to support auditing and logging services. This will help with establishing a consistent and standardized auditing framework.

This will be implemented using the common framework for Auditing within the Sanger Institute Integration Environment.