Description
...
- Step 3 - Data Export
- At each Export Interval as per defined in the configuration, a new POST call should be fired as below:
POST https://mypiwebapiendpoint/piwebapi/streamsets/recorded with the following JSON payload containing a section for each WebId corresponding to the tags
[
{"WebId":"P0dOJNBHKNtkyDm55BXnk92AAwAAAAU1JWR0RZUExNT1NJRDAzXENEVDE1OA",
"Items":[
{"Timestamp":"2018-01-16T20:31:50.267Z","Value":15308.23},
{"Timestamp":"2018-01-16T20:31:51.234Z","Value":15308.88},
{"Timestamp":"2018-01-16T20:31:51.357Z","Value":15308.04},
{"Timestamp":"2018-01-16T20:31:51.678Z","Value":15309.15},
{"Timestamp":"2018-01-16T20:31:51.907Z","Value":15309.65}
]
},
{"WebId":"P0dOJNBHKNtkyDm55BXnk92A3OM1AAU1JWR0RZUExNT1NJRDAzXEZPR0hPUk4uQ1JJTw",
"Items":[
{"Timestamp":"2018-01-16T20:31:50.653Z","Value":15308.67},
{"Timestamp":"2018-01-16T20:31:51.124Z","Value":15308.86},
]
},
]
- A successful request will provide a "202 Accepted" response
- The activities (request/reply) should be logged through EdgeX log service
- At each Export Interval as per defined in the configuration, a new POST call should be fired as below:
Possible improvements for the next version (Delhi Release):
...
- Possibility to perform data backfill (From StartTimestamp to EndTimestamp) - this may require an architectural change in Export Services
- Manage conflicts with overlapping tag names between different EdgeX deployments
...
- Support Kerberos authentication (Will need to specify in the configuration Keytab, Kdc, Principal and Realm)
Possible improvements for the long term:
- High throughput up to 100,000 events/second from each EdgeX node by using an ad-hoc OMF connector to send messages to PI Connector Relay with OMF
...