JSON is truncated as soon a timestamp is found

Getting Data In

I'm trying to read a json file generated by a ps1 script on Windows, but the UF keep truncating the json as soon it finds a valid timestamp. Removing the timestamp 'fixes' the problem, but I need the timestamps. I've a similar script running on unix machine and the issues is not appearing there. My props is the following:

[sourcetype_name]
TRUNCATE = 0
BREAK_ONLY_BEFORE_DATE = false
DATETIME_CONFIG = NONE
MAX_TIMESTAMP_LOOKAHEAD = 0
INDEXED_EXTRACTIONS = JSON

I'm starting to think that it's a bug on Windows UFs.

Get Updates on the Splunk Community!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

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

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...