We are forwarding some logs to Splunk Light Cloud using a Universal Forwarder. The inputs.conf on the forwarder successfully sends the logs and specifies a custom sourcetype . Within the Splunk Light Cloud ui, I am trying to edit the source type to do event breaks at a regex. However, it seems no matter what I use for the regex, it has no effect on the logs. Logs continue to be somewhat arbitrarily broken up, sometimes by timestamp and other times not at all. Our logs look like: nginx stderr | 2016/08/02 11:03:03 [info] 24#0: *5390 client closed connection while waiting for request, client: 10.0.30.16, server: 0.0.0.0:8000 nginx stdout | 10.0.30.16 - - [02/Aug/2016:11:03:15 +0000] "GET /health-check/ HTTP/1.1" 200 234 "-" "ELB-HealthChecker/1.0" "-" - 0.001 0.001 . nginx stdout | 10.0.31.218 - - [02/Aug/2016:11:03:15 +0000] "GET /health-check/ HTTP/1.1" 200 234 "-" "ELB-HealthChecker/1.0" "-" - 0.001 0.001 . nginx stdout | 10.0.30.16 - - [02/Aug/2016:11:03:45 +0000] "GET /health-check/ HTTP/1.1" 200 234 "-" "ELB-HealthChecker/1.0" "-" - 0.001 0.001 . nginx stdout | 10.0.31.218 - - [02/Aug/2016:11:03:45 +0000] "GET /health-check/ HTTP/1.1" 200 234 "-" "ELB-HealthChecker/1.0" "-" - 0.001 0.001 . This particular example all shows as a single event in the UI. But I'm trying to split at each nginx stderr | type prefix. Patterns I've tried so far: - \S+ \S+ \| , ^\S+ \S+ \| , ([\r\n]+)\S+ \S+ \| - .*\| , ^.*\| - stderr and ^.*stderr (just to try and see if I can get it to do anything) None of these appear to have any effect on event splitting. Looking in the "Advanced" section of the editor, the pattern corresponds to the BREAK_ONLY_BEFORE setting. But it won't let me manually specify other settings without overriding them on save. Anyone have any ideas? Thanks! ... View more