As a Splunk Cloud customer, should I contact Support to configure props.conf to enable event breaking to my specifications?

[jmajumdar]

Hello All
I just have question may be you guys can get me in the right direction . Looks like Splunk event breaking happens only in the indexer level. I have large groups of xml files that need to be in Splunk which I want to break in the word “someword" . I tried to put the below in the props.conf of the universal forwarder but it did not work; it completely ignored the props.conf. Then to play with it little more I downloaded the free version of Splunk Enterprise Security, I put the same props.conf in the indexer : /opt/splunk/etc/apps/search/local/props.conf and it worked. It is breaking the event exactly how I wanted it to. So I guess the event breaking needs to be configured only in the indexer or the search head level, NOT in the Universal forwarder? So as a Cloud customer, how should we approach this? Should I tell the Splunk support to configure the props.conf for us?
This is how I had the props.conf setup ;

[my_xml]
SHOULD_LINEMERGE=true
NO_BINARY_CHECK=true
BREAK_ONLY_BEFORE=someword
CHARSET=UTF-8
disabled=false

[esix_splunk · Accepted solution]

You could use a Heavy Forwarder with this props.conf on it on premise, or you can have Splunk Cloud Support install this indexer side. UF's dont have the ability to line break and parse like this fully.