This message originated from Cribl Community Slack.
Click here to view the original link.
It looks like the database collector is automatically turning MSSQL date and time fields into text versions of full timestamps complete with a hallucinated timezone. E.g.
'2025-06-26' --> "2025-06-26T00:00:00.000Z",
'13:09:11.0000000' --> "1970-01-01T13:09:11.000Z"
Is there a way to stop this behavior at the collector, or do I have to undo the damage in a pipeline?
Question
Database Collector Converting MSSQL Date Fields To Text With Hallucinated Timezone
+1I have seen this exact issue as well where our timestamps are Eastern time in the database yet the database collector adds Z to the end of, I guess assuming the times are supposed to be UTC. I had to remove the Z using a pipeline
Yes, it’s annoying having to un-mangle every date and time that’s not supposed to be UTC. Oracle DB collectors have the same issue. I’ve got over three dozen DB collectors and almost all have dedicated pipelines for fixing date/time fields.
There was a bug ticket created back in July 2025 when this was first reported, but I haven’t heard anything about a fix yet.
Sign up
Already have an account? Login
Login to the community
No account yet? Create an account
Using your Cribl Curious or University Account
User Login Employee loginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.