Difference between revisions of "Debug Monitor"

From DocDataFlow
Jump to: navigation, search
 
Line 1: Line 1:
 
A debug monitor is an [[Atomic adapter|''atomic adapter'']].  
 
A debug monitor is an [[Atomic adapter|''atomic adapter'']].  
  
It does not change the data flow: any input is passed unmodified through to the output.
+
It does not change the data flow: any input is passed through to the output unmodified.
  
 
Its function is to monitor the data flow and output some logging info to a log output somewhere. This could be a console log or a log file or some other form of log output.
 
Its function is to monitor the data flow and output some logging info to a log output somewhere. This could be a console log or a log file or some other form of log output.

Latest revision as of 03:08, 28 December 2013

A debug monitor is an atomic adapter.

It does not change the data flow: any input is passed through to the output unmodified.

Its function is to monitor the data flow and output some logging info to a log output somewhere. This could be a console log or a log file or some other form of log output.

Debug monitors can be switched on or off. During normal operations they'll normally be switched off, but when necessary, they can be switched on to help get an insight into the data flow, and help diagnose issues by giving an 'inside look' in the flow of granules passing through the adapter network.

In the Crawler system, there are provisions to easily attach a debug monitor to any named adapter in the adapter network by means of the top-level config file.