What do you look for first in an unfamiliar log file?

by

I’m working on Log Voyager, a browser-based log analyzer that keeps the selected file on your device.

While building the latest version, I noticed that my first steps are usually the same: identify the format, check the time range, find spikes in warnings or errors, and see whether the same failure keeps repeating with different IDs or timestamps.

That led me to add automatic format detection, an interactive event timeline, and grouping for similar errors.

I’m curious how other developers approach an unfamiliar production log:

1. What do you check first?

2. Do you begin with search, timestamps, severity levels, request IDs, or something else?

3. What usually makes existing log viewers frustrating for you?

I’d like to use the answers to decide what Log Voyager should add next.

1 view

Add a comment

Replies

Be the first to comment