Server Timestamp

Dev View
User View

The Server Timestamp property compound contains properties that allow the retention time of archived data to be defined in terms of the time when data was stored or updated. It comprises of the Server Timestamp Mode and Server Timestamp Index properties.

The server timestamp is defined as the time that a Core commits the given data to a data store (meaning the time at the particular Core that is committing the data, Master or Local), where committing refers to either the insert or update of persistent data. This is in contrast to source timestamps, which are the time at which data was generated (or retrieved) at a data source.

The server timestamp usage is controlled on the data store level, meaning that different Custom Time Series Data Stores can have different server timestamp usage configurations.

In the system, data is persisted in blocks rather than as individual values, meaning that values can have identical server timestamps related to the time that block of values was committed to the data store.

See the Server Timestamp Mode page for details on the different modes available for using and recording server timestamps.

See the Server Timestamp Index page for details on the different options available for the indexing of server timestamps.

The usage of server timestamps should be carefully considered before implementation. Be sure that the consequences of choosing a particular Server Timestamp Mode and Server Timestamp Index option are fully understood before making changes, particularly on systems with already populated data stores.