Solved: Re: Timestamp not added to CSV correctly

richgalloway · ‎07-10-2013

I've set up a DBConnect database input with output.format=csvh and output.timestamp=1. When rows are read, the timestamp is added as the first field, but without a comma separating it from the next field. Example:

"2013-07-10T13:58:36.601""FOO","000.00.42.12","Microsoft SQL Server Native Client","9.00.3042.00","Microsoft Corporation","1365739200.000"

I suspect this is a bug. Is there a work-around? I'm using DBX version 1.011.

---
If this reply helps you, Karma would be appreciated.

richgalloway · ‎10-08-2013

I installed DB Connect version 1.1.0 and the problem is resolved.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway · ‎10-08-2013

I installed DB Connect version 1.1.0 and the problem is resolved.

---
If this reply helps you, Karma would be appreciated.

Timestamp not added to CSV correctly

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Join the Conversation

Timestamp not added to CSV correctly

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence