Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #11629] Simplified event-history date and time representation #2397
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11629
Created by Tux12Fun on 2016-04-20 11:03:21 +00:00
my colleague asked me to have a look if a Service "xy" had a Problem at 12.04.2016 22:00.
It's very difficult to find such events if you have only have a view like: before 1 day 4 Hours or before 10th of April.
It would be nice if we could see Timestamps like 2016-04-12 22:00:00
And please display the Filter for 10, 25, 50 ... 500 (all events) at the History page.
2016-04-22 15:15:19 +00:00 by aklimov 6df8c37
2016-04-25 08:34:07 +00:00 by aklimov babaf15
2016-04-25 08:47:46 +00:00 by aklimov 062cb30
2016-04-25 09:07:17 +00:00 by aklimov a847e10
2016-04-25 10:29:07 +00:00 by aklimov c8b8618
2016-04-25 10:30:50 +00:00 by aklimov b4ffe5a
2016-04-25 11:28:11 +00:00 by aklimov 0ffb58b
2016-04-25 12:21:37 +00:00 by aklimov 25185b9
2016-04-26 09:34:10 +00:00 by aklimov 098eff9
2016-04-26 09:38:24 +00:00 by aklimov 531d999
2016-04-26 10:09:40 +00:00 by aklimov 809c2d0
2016-04-26 10:20:01 +00:00 by aklimov 1bef896
Updated by jmeyer on 2016-04-21 07:46:59 +00:00
That's reasonable, but I guess not the common case. I mean, "scanning" the history. If a user needs to got that far back, he'll most likely know exactly how far. And that's even the case for you: 2016-04-12 22:00:00
There's a feature open #10026 which is meant to improve this. For the meantime, convert this manually to a unix timestamp like so: timestamp>=1460496600×tamp<=1460493000
Waiting ages for a response isn't a nice thing either. ;) We removed this for a good reason: performance
You don't have to adjust the url manually, just scroll down to the bottom of the page and the next page of results should be shown automatically.
I'll close this as duplicate of #10026. If you have further questions, feel free to further ask them here.
Updated by jmeyer on 2016-04-21 08:47:29 +00:00
I'll re-open this as I had a discussion with a colleague myself. He has got an idea on how to improve the layout of the event history some time earlier which he will attach later today in this issue.
Updated by tgelf on 2016-04-21 09:06:22 +00:00
please have a look at the attached screen-shot. It shows a prototype created pre 2.1, a version that brought a lot of UI changes. The prototype was forgotten afterwards. With the current version titles would look different and the time would be shown below object state. However, I guess something like this would make "scan history with your eyes" much easier.
@Tux12Fun: could something like this be what you're trying to get? Regardless of visualization, we need of course better controls allowing us to choose specific time ranges in an efficient way.
I'd also opt for re-adding the "limit" control (but not the pagination). These are distinct beasts, limit controls how many rows to fetch at once, even when scrolling down. It doesn't involve evil "count" queries as a pagination showing a total page count does.
NB: One last note, as performance was mentioned -> we should get rid of permission-related joins when showing history for single objects. Permission control already took place when you arrive there. So this allows for much, much faster queries.