Integrations & Setup
Factry Historian
Creating a validation server
the historian server will present the measurements to the validation server by posting the following {{json}} format compatible with the historian bulk upload format example \[ { "uuid" "dad3f495 22b1 11ec 864a 81d3f45e479b", "name" "tank1 temperature", "description" "", "datatype" "boolean", "database" "historian", "collector" "opc ua staging", "tags" {}, "status" "active", "settings" { "nodeid" "ns=1;s=boolean 22", "collectiontype" "polled", "collectionoffset" 0, "collectioninterval" 5000 } }, { "uuid" "c54b4e3c 6f02 11ec 864a 81d3f45e479b", "name" "site1 tank2 temperature", "description" "", "datatype" "number", "database" "historian", "collector" "modbus", "tags" {}, "status" "active", "settings" { "regtype" "input register", "byteorder" "default", "collectiontype" "monitored", "modbusdatatype" "int32", "collectionoffset" 0, "collectioninterval" 2000, "address" 1 } } ] corresponding to the example request body, the following json message is expected for the response returned from the webhook \[ { "uuid" "dad3f495 22b1 11ec 864a 81d3f45e479b", "valid" false, "error" "should include site prefix" }, { "uuid" "c54b4e3c 6f02 11ec 864a 81d3f45e479b", "valid" true, "error" null } ]