The Timebase Data Collector connects to various data sources and establishes logging sessions with the Timebase Time Series Historian.
The Timebase Data Collector is an application that gathers data from various sources and logs that data into the Timebase Time Series Historian. Data sources supported include MQTT, SparkplugB, OPC UA, a Data Simulator, and an open source plug-in that can be used by the community to develop additional protocol support.
Logging Sessions
A logging session defines how and where data collected by the Data Collector is sent.
- A logging session connects to a single instance of a data source and data type.
- A logging session can target multiple historians but will only write to a single dataset within the targeted historian(s).
- Each session operates independently of other logging sessions.
- Each session has its own store and forward capability and buffer.
Store and Forward Functionality
The store and forward mechanism ensures data integrity even in unstable network conditions. Data is temporarily buffered locally and forwarded to the historian once the connection is restored preventing data loss during disruptions. The directory in which buffered data is stored can be configured by editing the appsettings.json file within the C:\Program Files\Flow Software\Timebase\Collector folder.
Data Collector FAQs
1. What Permutations and Configurations Are Allowed?
The Data Collector supports multiple logging sessions but only one protocol type per instance. For example, you can configure multiple logging sessions to target different datasets or historians. However, each collector instance supports only one protocol at a time, such as MQTT or OPC.
2. Can One Collector Have Multiple Collector Types?
No. Each collector instance is limited to a single collector type, such as MQTT, OPC, Data Simulator, etc. If you need to collect from multiple protocols, you will create multiple logging sessions.
3. Can One Collector or Logging Session Log to Multiple Datasets?
No. A single collector instance or logging session can only target a single dataset.
It is always a best practice to keep a 1:1 relationship between a logging session and a dataset. This makes it easier in the future to troubleshoot as well as backup or restore historic files.
4. When Running Docker, Do You Need to Spin Up Multiple Containers?
It depends. If you need to use different collector types (e.g., both MQTT and OPC), you will need to spin up multiple containers with one instance per type. However, if you are using the same protocol and want to log to a single dataset you can use a single container.
5. When Are Configuration Changes Picked Up?
The collector only detects configuration changes upon restart. Any modifications to the configuration file, including adding or adjusting logging sessions, will require a restart of the collector for the changes to take effect.