AWS ALB and Classic ELB Access Log Parser (Latency and Errors)

Reads ALB and Classic ELB access logs and summarises status codes, processing time and errors.

Use the tool

Why this tool exists

Load balancer logs separate the balancer status from the target status, which is the key to telling a 502 from the balancer apart from a 500 from the app.

The tool reads the quoted request, user agent and other fields correctly. A processing time of -1 means the balancer did not get a response from a target, and the summary counts those.

How to use it

  1. Download log files from S3 and unpack them, or drop the .gz files.
  2. Filter by ELB status if needed.
  3. Read status, latency and slowest paths.
  4. Switch to the table for details.

Frequently asked questions

What does -1 mean?

The balancer could not dispatch the request to a target or got no response in time.

Which fields are read?

The first 36 fields of the ALB format; later fields are ignored.

What if some lines do not match?

They are skipped and the result says how many. Network and Gateway load balancer logs use other formats.

Is my log uploaded?

No. Parsing happens in your browser and nothing is sent. Logs can hold IP addresses and tokens, so the page does not write them into the address bar.