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 Filebeat and Metricbeat modules, avoid introducing timestamp drift across daylight‑saving transitions, and remain compatible with existing configurations that rely on UTC fallback.

Questions:

• Should Beats treat an embedded offset as the event’s timezone by default?
• If automatic inference is enabled, what fallback should be used when the offset is missing or malformed?
• How can users opt‑out of the new behavior without breaking existing pipelines?