|
Wyatt Alt Scott Walker as Wyatt said, the ability to specify an endpoint other than the current time is kind of the point.
The specific Event Inspector (EI) desired use case that originally drove this ticket was trying to achieve a kind of freeze-frame picture of events from the latest report.
The problem with the existing ["=", "latest-report?", true] query is that if in EI users pull up a view of events from classes based on that query, spend two or three minutes looking at it and then try to drill in to a specific class, it's possible that relevant nodes will have submitted an updated report in the intervening time and there are no longer any events for that class that match ["=", "latest-report?", true].
The desired user experience is that when users first load EI they are presented with a view of the world as it looked at the time of page load. They should be able to muse over it, navigate around inside it, and expect consistency inside of it, at least until they refresh the browser.
Right now because EI makes multiple queries back to PuppetDB as the user is navigating around inside of it, to present that consistent freeze-frame of "current" events it seems like we would need some kind of ["=", "latest-report-before", "2013-10-30T14:55:00-07:00"]'.
That's the use case that originally drove the ask in the ticket.
|
