Getting Data In

Debugging LINE_BREAKER and TRANSFORMS

mzorzi
Splunk Employee
Splunk Employee

Are there any DEBUG settings I can enable to get more information on how LINE_BREAKER and TRANSFORMS settings are applied at index-time?

Tags (2)
1 Solution

jrodman
Splunk Employee
Splunk Employee

The category.regexExtractionProcessor log category should produce errors for some categories of failing to compile the TRANSFORMS regexes. You could turn up its verbosity to get success messages when building them as well. They do not have debug output after the first matching event comes through.

I've generally found it necessary to use a combination of pcretest, test instances/indexes, bogus fields, and careful tests to determine the cause of TRANSFORMS troubles.

Line breaking similarly will produce output saying what conf is loaded for category.LineBreakingProcessor, ie for a given conf/source/sourcetype, it will say what the truncation length is as well as the lookbehind (if these are set).

View solution in original post

jrodman
Splunk Employee
Splunk Employee

The category.regexExtractionProcessor log category should produce errors for some categories of failing to compile the TRANSFORMS regexes. You could turn up its verbosity to get success messages when building them as well. They do not have debug output after the first matching event comes through.

I've generally found it necessary to use a combination of pcretest, test instances/indexes, bogus fields, and careful tests to determine the cause of TRANSFORMS troubles.

Line breaking similarly will produce output saying what conf is loaded for category.LineBreakingProcessor, ie for a given conf/source/sourcetype, it will say what the truncation length is as well as the lookbehind (if these are set).

Got questions? Get answers!

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

Meet up IRL or virtually!

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

Get Updates on the Splunk Community!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...