aogburn/yala

Yet Another Log Analyzer

yala's Issues

Improve access log sanity check speed

This could be simplified and run faster based on a first (earliest) and last (latest) log line comparison.

Clickable file links

It could be handy to have clickable file links of files summarized by yala

Stuck thread summaries

If stuck thread logging is present, it'd help to summarize these (peak stuck thread counts, summary of stuck time, and summary of thread calls).

Transaction abort suggestion

May help to look for and report suggestion of transaction aborts

2023-07-31 14:10:49,620 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 6) ARJUNA012095: Abort of action id 0:ffff0a180002:a7a0891:64c6d76d:30e0b invoked while multiple threads active within it.
2023-07-31 14:10:49,625 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 6) ARJUNA012381: Action id 0:ffff0a180002:a7a0891:64c6d76d:30e0b completed with multiple threads - thread default task-79 was in progress

See if handling of 'binary' log file can be improved

A error may be missed in some irregular file encodings (03714910)

Identify time gaps

Flag log lines where the time gap exceeds a specified interval.

For example, if the interval is 10 seconds, it would identify lines 2 and 3 below, as there is an 11-second gap between them:
2023-06-01 12:42:32,760 WARN log line1
2023-06-01 12:42:42,760 WARN log line2
2023-06-01 12:42:53,760 WARN log line3
2023-06-01 12:42:54,760 WARN log line4

This could be used to identify bottleneck events and also periods of time when the application is not busy.

By thread log parsing split

Sometimes we need to follow events of individual threads in line. So a flag to parse out events to individual thread sub files could be helpful.