Failed to parse date field [@timestamp]: unable to parse date when timezone offset present but no timezone configured
Failed to parse date field [@timestamp]: unable to parse date when timezone offset present but no timezone configured Goal: Determine whether Elastic Beats should automatically interpret timezone offsets embedded in log timestamps when no explicit timezone setting is provided in the input configuration. Constraints: The behavior must be consistent across Fil
beats