GC Log Analyzer 26.10.0

Table of Contents

Need help?

Schedule a consultation with an Azul performance expert.

November 2, 2026

What’s new

GC Log Analyzer now parses and visualizes TICKSTATS and TICKCLIENT records in a new Tick Profiler chart section, with six charts:
- Tickstats Ticks and Tickstats Entries - raw per-tier counts across C1, Dolphin, Dolphin OSR, Mid Tier, Final Tier, LVB-Less, and Unaccounted.
- Tier Distribution (stacked) - cumulative percentage of total ticks per tier, anchored by a flat Total (100%) reference line. The gap between two consecutive lines is the share of that tier.
- Tier Distribution - each tier’s individual, non-cumulative percentage share.
- Client Ticks and Client Entries - one line per distinct TICKCLIENT client name, discovered dynamically when the log is opened.

When chart times are displayed as absolute timestamps (any of the Absolute Time options under View > Time Units), the toolbar time selection fields now display and accept date and time values instead of seconds. The field label changes to Time selection (date):, and hovering over it shows the time zone in use.
- Enter timestamps in the format yyyy-MM-dd HH:mm[:ss[.SSS]], for example 2026-10-01 09:30:30.123. Values are interpreted in the currently displayed time zone. You can also append Z or a UTC offset, for example 2026-10-01 15:00:30+05:30.
- If a value cannot be parsed, the field is highlighted and the warning button next to the fields shows the error message, including the value you typed.
  
  This makes it easier to jump directly to the time of an event recorded elsewhere, such as an application or network log, without converting it to JVM uptime seconds.

A new Horizontal Time Labels option under View > Time Units displays the X-axis time labels horizontally instead of rotated by 90 degrees, making absolute timestamps easier to read. The setting is remembered between sessions.

Issue ID Description

Issue ID	Description
GCLA-744	Boolean log fields recorded as `1`/`0` (for example, in `CNCPRODUCTIVITY` records) were always parsed as `false`.
GCLA-747	GCLA could drop log lines where the uptime decorator is padded with spaces, for example `[ 2.827s]`.
GCLA-751	Opening a truncated Zing GC log with no VM header, and therefore no JVM start time, failed with a `NullPointerException`.

GCLA-744

Boolean log fields recorded as 1/0 (for example, in CNCPRODUCTIVITY records) were always parsed as false.

GCLA-747

GCLA could drop log lines where the uptime decorator is padded with spaces, for example [ 2.827s].

GCLA-751

Opening a truncated Zing GC log with no VM header, and therefore no JVM start time, failed with a NullPointerException.

There are no new known issues associated with this release.