Introduction
  • 05 Jun 2023
  • 2 Minutes to read
  • PDF

Introduction

  • PDF

Article summary

N3uron Historian is a high-performance time-series storage system based on a MongoDB database. In x64 bit systems, the MongoDB instance is automatically installed in the N3uron installation folder, so that Historian is ready to store data as soon as the installation is complete. In addition, an external MongoDB database can be used instead of the embedded MongoDB instance. Data can also be stored simultaneously in multiple Historians. In x32 and ARM architectures, the user may first install MongoDB and configure Historian to store data in the external MongoDB instance.

N3uron Historian can store any tag values that have been collected locally in the same node, or those collected remotely by other nodes and received in the Historian node through N3uron Links. It also provides a built-in Store & Forward mechanism that stores data locally in case of communication loss between N3uron and the database.

Historian provides efficient data compression and partitioning mechanisms, allowing for massive volumes of time-series data to be stored without reducing its performance over time. As a reference for disk usage estimation, 1GB of hard drive stores approximately 100 million events (value changes).

49-n3uron-historian-configuration-example

Data stored in Historian can be retrieved using the following methods:

  • WebUI: Includes a rich HTML5 interface to retrieve and visualize data in charts and data tables (raw and aggregated data). Data can also be exported to CSV files. The historical data retrieved can be located in the same N3uron node as the WebUI or in a different N3uron node, providing that the nodes are connected through a N3uron Link. 
  • REST API Server: Using the optional REST API Server module, historical data can be retrieved in JSON format using REST API calls (raw and aggregated data). The historical data retrieved can be located in the same N3uron node as the REST API server or in a different N3uron node, providing the nodes are connected through a N3uron Link. Several examples of historical data retrieval can be found in the Rest Api Server Manual. 
  • OPC UA Server: The OPC UA Server module supports Historical Data Access, thus allowing an OPC UA Client to fully access historical data.
  • WebVision: Includes a component to retrieve and visualize data in charts and data tables similar to the interface provided by WebUI. Data can be also exported to CSV files. The historical data retrieved can be located in the same N3uron node as the WebUI or in a different N3uron node, providing that the nodes are connected through a N3uron Link. 
  • MongoDB Client (for example, MongoDB Compass): Direct connection to the MongoDB database to retrieve data in raw mode.

historian-architecture-n3uron



Was this article helpful?

What's Next