Seeq Connector

overview the factry historian connector enables seeq to access data from factry historian https //www factry io/historian/ this includes signal data, asset tree data, uoms and capsules prerequisites the factry historian connector is compatible with factry historian version 6 1 and higher configuration this is an example configuration template that is displayed in the additional configuration box that appears when you click configure for an existing datasource (or if a new datasource is being created, in the create new datasource connection modal that appears after clicking add datasource) on the datasources administration page { "uri" "http //myhistorian company dev 8000", "organizationuuid" "b6fa43ca add8 11ed 907d 1234ac170004", "accesstoken" "eyjhbgcioijiuzi1niis hgyxtdtqtctn2vq9i" } factry historian additional configuration property name default value data type description uri null string the url used to connect to factry historian for example http //myhistorian company dev 8000 http //myhistorian company dev 8000 organizationuuid null string the uuid of the organization you wish to consult data from you can find the organization uuid in the historian admin interface under configuration > server settings > organizations accesstoken null string/ secretfile the api access token used to communicate with the factry historian api you can find more information on how to create an api token here https //docs factry cloud/docs/historian/v6 1/administration/users/#api tokens known issues only factry historian measurements of type number, boolean and string are supported for indexing arrays and raw data types are not indexed performance consideration prior to version 6 3 of factry historian the historian has a fixed timeout for queries this may cause some issue while fetching data over longer time periods, for example a couple of months this issue can be resolved by limiting the "max results per request" configuration value to a value of around 100000