Refine your search:

Something's up with the batch processor. I send the following file to a sink and it doesn't set any of the metadata fields as it used to previously.

Also documented at http://www.splunk.com/base/Documentation/latest/Data/Assignmetadatatoeventsdynamically

dummy.log

***SPLUNK*** host=something source=keyboard sourcetype=text
this is an event!

Subsequent processing of props and transforms don't event happen. The event get's indexed as if I never specified the header.

Fails on a fresh Splunk 4.2.2 (build 101277) on Windows 7 64bit but works Splunk 4.1.7 (build 95063).

PS I noticed another post with a similar problem http://splunk-base.splunk.com/answers/9110/batch-input-doesnt-honor-line_breaker-settings

asked 22 Jul '11, 14:07

Marinus's gravatar image

Marinus
72912
accept rate: 45%

edited 03 Aug '11, 10:50

Lowell's gravatar image

Lowell ♦
9.6k637


One Answer:

Just received a reply from support, the behavior is now configurable via props.conf by modifying the HEADER_MODE param.

[source::/tmp/splunk/var/spool/splunk]
HEADER_MODE = always
link

answered 02 Aug '11, 11:35

Marinus's gravatar image

Marinus
72912
accept rate: 45%

Post your answer
toggle preview

Follow this question

Log In to enable email subscriptions

RSS:

Answers

Answers + Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×187
×137
×94
×72
×4

Asked: 22 Jul '11, 14:07

Seen: 782 times

Last updated: 03 Aug '11, 10:50

Copyright © 2005-2012 Splunk, Inc. All rights reserved.