Add more granularity to Cerberus server log timestamps

Dale Westrate

• June 17, 2025 19:26

Currently, Cerberus can only log down to the millisecond (yyyy-MM-dd HH:mm:ss,SSS).  On a busy server, it's not granular enough when troubleshooting things, since multiple log entries can have the same timestamp.  For example, a moment ago I cherry-picked a log file and easily found four different server threads that had logged six entries within the same millisecond.  This would be problematic if I had a concern that different threads were doing something unexpected, or if timing were a concern for some reason.

Something more granular (preferably nanoseconds) would be very useful.

0

• 

  Connor Woolfolk

  Community Manager

  • June 18, 2025 14:22

  Hello Dale,

  Thanks so much for sending this enhancement request over. I'll get it over to our Product and Dev teams for their review, and we'll be back in touch either here or through a ticket if we find that we need more information.

  0

Please sign in to leave a comment.