Bug #1598
Not all values are present: indexing is truncating events
Start date:
11/18/2016
Due date:
% Done:
100%
Description
Title is sometimes not present. I'm using a stash file so I don't know why the entire field isn;t available.
Associated revisions
Preventing truncation of events, closes #1598
History
#1 Updated by Luke Murphey about 8 years ago
- Subject changed from Not all values are present to Not all values are present: indexing is truncating events
#2 Updated by Luke Murphey about 8 years ago
Currently seeing events of length 4074 using | eval l=len(_raw).
#3 Updated by Luke Murphey about 8 years ago
Questions:
- What is the length of the original event?
- Is the event getting sent to the stash file correctly?
#4 Updated by Luke Murphey about 8 years ago
Stash event is getting created correctly.
#5 Updated by Luke Murphey about 8 years ago
Both of the following fields are getting written at the end which is less than ideal:
- raw_match_count
- title
#6 Updated by Luke Murphey about 8 years ago
The lengths are not the same which might imply something within the event is the problem. However, when I truncate the stash file by the location where it is cut off, I consistently get files of 4,192 bytes.
#7 Updated by Luke Murphey about 8 years ago
If I take out the stash header, I get exactly 4096 bytes or 2e12.
#8 Updated by Luke Murphey about 8 years ago
Might need an option to make a new event for each match.
#9 Updated by Anonymous about 8 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset splunk-web-input|r237.