You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The timestamp ts is in milliseconds format (with microseconds precision?), which may cause trouble for log collectors like Fluentd; see this ticket as an example.
Is this extra precision for timestamp really needed for component such a cert-manager? Wouldn't be unix-time in seconds enough to make the log processing smoother 🙏🏼 ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey 👋🏼 guys,
I have question that have yet to be asked, as far as I can tell, so I'm here.
Currently, the log from cert-manager, running in k8s, looks like this, at least when you have
--logging-format=json
:The timestamp
ts
is in milliseconds format (with microseconds precision?), which may cause trouble for log collectors like Fluentd; see this ticket as an example.Is this extra precision for timestamp really needed for component such a cert-manager? Wouldn't be unix-time in seconds enough to make the log processing smoother 🙏🏼 ?
Beta Was this translation helpful? Give feedback.
All reactions