What I did when facing a similar situation recently was create an infotable type logged property on my thing with a datashape containing the fields I wanted to trap from the event (e.g. maybe for you it is event name, event duration/value, event timestamp... if the value stream timestamp is somehow not appropo). That would give you an ongoing history of events you could query from the value stream (and perhaps purge over time ultimately too).
I then subscribed to data changes on that property and generated whatever property updates and events I want for performing more specific actions on particular types of event names that are received.
