Log Timestamp Normalizer
Formats detected
ISO 8601 / RFC 3339 (with or without a timezone), RFC 2822, Apache/Nginx access-log timestamps, syslog (RFC 3164, year inferred), common database timestamps with fractional seconds, US and European slash/dot dates, and Unix seconds/milliseconds/microseconds (range-checked against a plausible 1990–2100 window so an unrelated large number doesn't get misread as an epoch time). Timestamps embedded inside a longer log line are found by scanning the line, not just full-line matches.
What "confidence" means
high the format was unambiguous and complete — year and timezone both came from the source text. medium something was inferred but from an explicit, visible choice you made (a reference year, an assumed source timezone). low the date itself was genuinely ambiguous (day/month order) and was resolved by your ambiguity setting rather than anything in the source. Every inference is also spelled out in that row's note — nothing is silently assumed.