Better timestamps on Scheduled Config Backup files
I copied this format from another user, seemed pretty functional.
- What is the problem that this feature would fix?
In Event Manager->Scheduled Tasks, the current variable “{{T}}” returns a decimal representation of the “Unix” current date and time. My most recent Scheduled Backup event gives filenames like “<servername>_config_1740602199.zip” where “1740602199” is the timestamp.
- Why is it a problem?
That timestamp value is not really human readable. While there is also the date/time stamp in the file system, if the file alone is copied this may not represent the actual time of the backup event.
- Is there a workaround you currently have for this problem?
Not really. That Unix timestamp value could be translated but only manually.
- Do you have a suggestion on how you would like to see the problem fixed?
I should think the developers could remedy this by using a formatting function – translate that Unix timestamp value into something like “20250226_1305” showing the sortable date format followed by the time value. Users/admins can tell immediately when the backup was generated.
- How big is the problem?
This only affects Cerberus and server admins but in the event of a restore being needed, being able to immediately know one has selected the correct backup from which to restore.
-
That last bullet should read "one has selected the correct backup from which to restore would be very helpful."
0 -
Hello Paul,
Thanks so much for taking the time to submit this enhancement request. I do believe having timestamps be a bit more digestible would be a good plan, and it looks like we have enough information here to get this in front of our Product team. As soon as I have an update, or need more information around this request, I will be sure to reach out here or through a ticket.
0 -
Hello Paul,
I just wanted to let you know this should be making it in to an upcoming release, so be on the look out for it!
0 -
Connor, another similar one: when one exports the user list to csv, the columns "Password Last Changed Date", "Create Date" etc. all seem to have that numeric value. Can we consider that too?
Paul
0 -
Hello Paul,
I'll reach out to the Dev team to see if that's included in this update as well, I do know they did change a few other places that had this same timestamp format, once I get word back I will be sure to update this thread.
0 -
Hello Paul,
I got word back that, a change in those CSV exports will have a bigger range of effect than just that one report currently, so while this change is not currently on the roadmap, it's certainly something we can consider in future releases. Luckily if it downloads into an excel sheet, there should be a formula out there that can convert it into something a bit more readable, for the time being.
0
Please sign in to leave a comment.
Comments
6 comments