Access log time stamp reporting in epoch's millisecond time

[zeeIBM]

@xiaofan-luan @yanliang567

In milvus access logs configruation, I see these time fields are available to be used:

$time_cost | Time taken for completing the access
$time_now | Time at which the access log is printed (usually equivalent to $time_end)
$time_start | Time at which the access starts
$time_end | Time at which the access ends

Can these be configured to report epoch time in milliseconds?

I am assuming they are currently taking milvus server locale time zone information and reporting in that in the accessLogs?

[xiaofan-luan]

@xiaofan-luan @yanliang567

In milvus access logs configruation, I see these time fields are available to be used:

$time_cost | Time taken for completing the access $time_now | Time at which the access log is printed (usually equivalent to $time_end) $time_start | Time at which the access starts $time_end | Time at which the access ends

Can these be configured to report epoch time in milliseconds?

I am assuming they are currently taking milvus server locale time zone information and reporting in that in the accessLogs?

yes, right now they are using local timestamp.

I don't know what data format is used right now. but modified it shouldn't be hard

[zeeIBM]

Hello @xiaofan-luan @yanliang567,

I’ve observed that the following access log time fields in Milvus are currently in UTC, and there doesn’t appear to be an option to change the timezone:

$time_cost — Time taken to complete the access

$time_now — Time when the access log is printed (usually same as $time_end)

$time_start — Start time of the access

$time_end — End time of the access

This UTC behavior works well for our use case. However, our logic assumes that these timestamps will always remain in UTC. If users are ever allowed to change the timezone (e.g., via configuration or environment variable), it could break our feature.

Could you please confirm whether Milvus provides any mechanism to change the timezone for these log values? I just want to be sure we're not overlooking such a capability.

Thanks in advance for your insights!

[yanliang567]

@aoiasd any ideas?

[aoiasd]

Now we use the local timezone as default timezone. It only changes when you change you system local timezone(linux/macos at /usr/share/zoneinfo).
We chould support set timezone if needed.

[zeeIBM]

@aoiasd

Sorry, My question is different. Is the timestamp format in Milvus access logs always guaranteed to be in UTC? We're depending on UTC format — if a user can change it to another format, it would break our feature. is such control of changing the time format given to a user?

[zeeIBM]

So in mycase I took your standalone dockerized milvus - I got UTC timestamps by default. I would have to experiment in docker to change its time zone and see if it still logs UTC time stamps or not.

That would give the answer for current behavior.

[aoiasd]

So in mycase I took your standalone dockerized milvus - I got UTC timestamps by default. I would have to experiment in docker to change its time zone and see if it still logs UTC time stamps or not.

That would give the answer for current behavior.

Not guaranteed to be UTC, but timezone won't be changed after you start milvus. ONLY If you change pod system timezone before you start milvus, it will be changed.