Solving the Problem

Last update: 2022-10-04
  • Created for:
  • User

Read more about Data Workbench’s End-of-life announcement.

When a web server goes offline because of a failure, the solution is a simple one that requires a Data Workbench user with appropriate privileges to open the Log Processing Mode.cfg file and add the ID of the Sensor (in our example, WEB2) to the “Offline Sources” section.

This section of the file tells the data workbench server that it should no longer expect any data from this source because it is, in fact, offline.


This change does not need to be performed by an Adobe Consultant. Anyone who has appropriate privileges to open the Log Processing Mode.cfg file can make this change.

If WEB2 begins to send data again, the data workbench server brings the source back online and adjusts the As Of time to reflect the last time it received data from all of the sources of which it is aware. In other words, new data coming into the system takes precedence over what is written in the Log Processing Mode.cfg file.

If WEB2 goes offline again, the As Of time will again stop, and you will need to edit the Log Processing Mode.cfg file again even though it might already have WEB2 listed as an offline source. This is an artifact of the design of the product in keeping with the definition of the As Of time: the last time the system has data for all known sources.

When you add more web servers (WEB4, WEB5, WEB6), and they begin sending data to the data workbench server, you do not need to do anything to have the data workbench server recognize the new sources. The system simply becomes aware that it should be expecting data from these new sources, as described above.

On this page