I understand the OSIsoft connector leverages a secure TCP/IP socket to connect to the OSIsoft PI Historian WebAPI interface. The TCP/IP socket guarantees delivery of the data assuming the Ethernet connection is available. How does the connector handle network down scenarios?
The OSIsoft Connector running on Flexy has the ability to buffer ~250,000 samples when the WAN connection is down. The number of samples is based on the remaining memory on the heap. As long as the device on not low on memory it will be able to store more tags.
The buffer is implemented as a last in first out (LIFO). Timestamps are associated with each sample in the LIFO. When the WAN network is available the LIFO is emptied as quickly as possible depending on the loading of the Flexy. The Connector is not the highest priority function running on Flexy.
The amount of time the system can support a back-haul network (WAN) outage is dependent on the sample rate and the number of samples being captured. The higher you sample rate is, the less time you will be able to tolerate a connection outage.
When the buffer runs out of memory, the connector discards the oldest data buffered in preference of the newest. When the connector comes back online, the latest data collected will be sent to OSIsoft.
The offline data buffer is in volatile storage, therefor if your device loses power, the tags not already sent to OSIsoft will be lost.
Topic closed due to inactivity.