- This topic has 2 replies, 2 voices, and was last updated 10 years ago by .
-
Posts
-
When I sort by last boot time and total up time, I notice they get out of order.
For example with uptime:
Sorting from low to high I see
0d
111d
113d
118d
174d
19d
1d
200d
214d
25d
28d
2d
With Last Boot Time sorted the same way I see
10/1/2014 11:25
10/1/2014 08:09
10/10/2014 05:01
10/2/2014 13:22
10/20/2014 17:30
10/20/2014 08:36
10/22/2014 12:31
10/3/2014 21:51
3/29/2014 05:00
4/12/2014 07:43
5/23/2014 09:42
5/31/2014 08:33
5/7/2014 14:42
5/9/2014 09:51
6/20/2014 15:42
6/30/2014 14:47
7/10/2014 04:00
7/3/2014 05:00
7/8/2014 06:05
8/21/2014 15:32
8/22/2014 23:56
8/28/2014 05:17
8/31/2014 15:01
8/5/2014 15:50
Now, I realize why it’s doing this. This is just how the computer sees the numbers, but is there any way to make it behave like a normal date sort instead of value in this case?
For uptime, I know that’s more difficult.. Or at least, I think it would be. One fix idea is to have an option to preceed the number reported in days with zeros so that it would sort correctly. Some people might not think that’s a very pretty option, but when you’re using it to sort for uptime having
000d
111d
019d
001d
200d
214d
025d
028d
002d
kinda makes it easier to read.
Maybe there’s another way to have these sort better, but when you’re dealing with 200 servers a night for 7 days in a row and looking at uptime, trying to figure out what has been up longer than 30 or 60 days, your eyes start bleeding eventually, and you get sloppy and miss stuff. (Or at least I do.) If they sorted in actual date range instead of the numeric value that’d be a major help. 🙂
Thanks, Travis. I totally hear your frustration on this one and agree that proper date sort would be nice. From a technical perspective I think we looked at this before and ran into an unexpected problem with the implementation and so we put it on-hold. However, we do still plan to get it implemented in a future build.
-Doug
- You must be logged in to reply to this topic.