MongoDB, is actually a historian?

General Discussion
, ,
1

Need the community knowledge and opinions

With SQL Historian, Ignition Performs historian algorithms to store and query data. (Actually a Historian with deadbands, interpolation and more)

Does the Mongo Connector does something similar? Is this managed by Mongo when using a Time-Series database and Ignition only should insert documents?

The way data goes into Mongo from Ignition is based on mongodb.insertOne() or mongodb.insertMany(), Is this the only way to insert data?

Should I perform a script algorithm to perform historian and decide when to store or not data?

2

Have you asked the people who make your Mongo connector?

3

Yes

4

Currently the MongoDB connector has the goal to visualize data from a Mongo Database. We have not given it any ability to store historical data from the Ignition platform out of the box. We have had talks about expanding what is possible with this connector, but they are just discussions at this point. Query tag functionality would likely be the next step in adding functionality.

As you have mentioned, we do offer scripting functions to add and update data within a Mongo database, but there isn’t anything built into Ignition that doesn’t involve some work on your part to be able to modify data within a Mongo database.

Garth