Date/Time Range Filter

Pinpoint the exact window that matters. Date/Time Range Filter slices any log by a start and end timestamp, keeping only the lines inside your chosen window.

It reads the wide variety of timestamps logs actually use — ISO 8601 (2025-06-11T14:00:00Z), space-separated (2025-06-11 14:00:00), Apache/nginx bracketed ([11/Jun/2025:14:00:00 +0000]), syslog month-day (Jun 11 14:00:00) and Unix epoch in seconds or milliseconds — and reports how many lines fell inside the window, outside it, or lacked a recognizable timestamp entirely.

Because each line is parsed independently, you don’t need every line in the paste to share the same format. Mixed-source pastes — an app log next to a proxy log, or a syslog snippet next to a JSON line — filter correctly as long as each line starts with one of the supported timestamp shapes.

• Start + end window — inclusive bounds; a line exactly on the boundary is kept.
• Format-agnostic — ISO 8601, Apache/nginx brackets, syslog, and epoch seconds/milliseconds, auto-detected per line.
• Unbounded ranges — leave start empty for “from the beginning” or end empty for “to the end.”
• Untimed lines — keep or drop lines where no timestamp could be parsed, via a checkbox.
• Live counts — total, in-range, out-of-range and no-timestamp tallies update on every run.
• Plain-text output — the kept lines appear ready to copy, in their original order.

1. Paste your log lines into the text area — mixed formats are fine.
2. Pick start and/or end with the datetime pickers, or leave one blank for an open-ended range.
3. Toggle “Keep untimed” if you want lines without a parseable timestamp included in the output instead of dropped.
4. Filter. Only lines whose timestamp falls within [start, end] remain, and the stats row shows exactly how many were kept, excluded or unparsed.
5. Copy the windowed slice for further analysis or to paste into an incident channel.

Example 1 — Incident window. An alert fired at 14:03; set start to 14:00 and end to 14:05 to isolate everything around the spike and cut the rest of the day’s noise.

Example 2 — Slow query hunt. A user reports slowness “around 2pm” — slice the database log to that exact minute instead of scrolling through hours of entries.

Example 3 — Daily audit window. Recreate the same working-hours window (say 09:00–17:00) each day by adjusting only the date portion of the pickers, keeping the review process repeatable.

Example 4 — Deploy correlation. Set start to the deploy timestamp with an open end, then scan the “in range” lines for the first error that appeared after the release went out.

• Precision — exact inclusive boundaries instead of eyeballing where a window starts and ends.
• Broad format support — no need to pre-normalize timestamps across ISO, Apache, syslog or epoch before filtering.
• Transparent — the in/out/unparsed breakdown means you always know what happened to every line, not just what survived.
• Mixed-source friendly — each line is parsed on its own, so combined logs from different tools still filter correctly.
• Private — filtering runs entirely client-side; pasted logs never leave the page.