it's possible to drop a nested field in case the value is empty?
this is a workaround to avoid mapping issues, as other application logs are creating fields like:
log.business_information is mapped as an object. In case an event with empty value will appear, this event is lost due mapping conflict:
object mapping for [log.business_information] tried to parse field [business_information] as object, but found a concrete value"