InSight is capable of supporting 3 history modes: no history, in-memory history in the terminal (default), history logged to the controller.

In-memory history is kept on a device-by-device basis.  Each device has its own history buffer.  History buffer size defaults are set so that a) in most cases, there is history back to the start of a transaction and b) if there is a problem and the terminal is dumped, there is enough history to figure out what led up to the problem.

History kept on the controller is a feature that we haven’t fully decided how to implement (and that we are looking for feedback on).  It is not currently in the planned Version 1 feature set.   Here are the kinds of question we have yet to answer: If we were to keep 2 or 3 days history for critical devices (system display, keyboard, scanner, printer?), just how much data is that?  How much LAN traffic is it?  Would customers need it for all registers always, or would they just turn it on for a register or range of registers when they are trying to track down a problem?  Does the InSight ‘snapshot terminal dump’ and in-memory history meet 99% of the requirement?