Announcing Graylog Illuminate v7.0.3

Announcing Graylog Illuminate v7.0.3

Release Date:  January 15th, 2026

 

FIXED

  • Apache HTTPD: Issues parsing HTTP timestamp (3239)

    • When extracting the HTTP timestamp and casting it as a date/time data type the grok engine relies on the locale setting, potentially resulting in parsing errors. This change disables that casting and renames the field http_timestamp to vendor_http_timestamp to avoid indexing errors and make clear that the value reflects exactly what was extracted from the source data.

  • Apache HTTPD: Unparsed date value applied to event_created (3244)

    • The Apache HTTPD processing pack has strict requirements for the Apache log file names which may limit the Apache logging configuration flexibility. This change relaxes the field names to allow prefixes, but the filename prefixes must be followed by a non-alphanumeric character such as an underscore or dash.

 

CHANGED

  • Apache HTTPD: Log source identification is too strict (3240) 

    • The Apache HTTPD processing pack has strict requirements for the Apache log file names which may limit the Apache logging configuration flexibility. This change relaxes the field names to allow prefixes, but the filename prefixes must be followed by a non-alphanumeric character such as an underscore or dash.

  • BIND DNS: Changed parsing for client query messages to capture optional `key` and `view` values. (3226)

 

Let us know what you’d like to have included in our GitHub issue tracker.

Get the Monthly Tech Blog Roundup

Subscribe to the latest in log management, security, and all things Graylog blog delivered to your inbox once a month.