LogScale provides comprehensive timezone support for query functions, with a detailed list of supported timezones across Africa, America, Antarctica, Asia, Atlantic, Australia, Europe, Indian, and Pacific regions. The documentation outlines how to handle timezone offsets with UTC/GMT, explains why abbreviations are not supported due to ambiguity, and demonstrates how to use match expressions to map between unsupported abbreviated timezones and accepted formats.

LogScale supports the time zones listed in the table below. These time zones are used in time-related Query Functions. The specific time zones available depend on your LogScale release version.

A sample list of timezones is shown below, please confirm the correct list of timezones according to your Java version using the corresponding JDK documentation.

The time zone identifiers UTC and GMT can be appended in queries with an offset for example, timezone="UTC+02:00".

Care should be taken with time zone abbreviations as some of them have ambiguous or redundant meanings. An example of this is the CDT abbreviation which has multiple meanings:

To resolve such ambiguities, you can map between unsupported abbreviated time zones to accepted time zones using a match expression. For example:

dateTime match {
    /CDT/ => findTimestamp(field=dateTime, timezone="UTC+10:30");
    * => findTimestamp(field=dateTime);
}

To maintain such a mapping in one place only, it could advantageously be turned into a saved query. For more information on how to create saved queries, see Save Searches.