Dropping stacktrace Lines after greedy data

Elastic Stack Logstash
1

I've got these lines that are after my greedy data similar to these:

at au.com.xxx.etrading.xxxxx.messaging.tum.AbstractTumProtoSubscriber$TumProtoEventListener.go

and logstash attempts to process them thereby generating a lot of stack trace errors like these:

BulkShardRequest [[logstash-2017.08.16-pf][2]] containing [14] requests
org.elasticsearch.index.mapper.MapperParsingException: Could not dynamically add mapping for field [Thread.java]. Existing mapping for [Thread] must be of type object but found [text]

They come right after my greedydata line. How do I drop the first lines so they don't get processed so I can avoid all the errors.

2

Didn't you recently ask the same question in another thread?

Instead of deleting useful stacktrace line you should use a multiline codec to join the lines of the stacktrace with the log message they come from.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.