Allow to include open Event Frames
The integrator only includes EventFrames that are closed (have end time). That is not included in the documentation, so a major issue for me now.
The reasoning is that an open EF may not have all data or correct data. I would prefer to let the user decide on that and allow to include open eventframes. After all we can filter out the open ones using row filters.
I planned to use the integrator to get rid of OLEDB Enterprise. Now it turns out i cannot reach all my data. Looking seriously into returning the license.
The reasoning is
Barry Hu commented
To make the whole thing really useful (including PI AF upstream) it would need to
1. Publish open event with a start time
2. As event end, automatically recapture attributes and reevaluating naming pattern for events
3. Automatically update data on Integrator
Echoing other comments here: we were looking to use event frames to track downtimes and use the streaming feature of the PI Integrator to send those downtimes to our reporting platform in near realtime
For lack of this feature we will have to look into another solution.
Very hard to understand why this is already done from technical perspective. This is possible using PI System Access and PI Data Link. The data is there, you just need to publish it :(
I have the EXACT same issue. We were planning on using the integrator for near realtime publication of data to 3rd party systems that do not have a PIAPI that can read event frame data. This is causing a major issue since we have to wait weeks for the data to be available.
This is a key feature for use with RtDuet, as open event frames are in-progress downtime events.
Without it, we will likely use RtTech's Report Sync feature instead.
We also are desperate for this feature. We need to report on open event frames for a number of applications. OLEDB Enterprise is our only option at the moment for PowerBI reports