FortiWeb
A FortiWeb can be configured to join a Security Fabric through the root or downstream FortiGate.
satoh
Staff
Staff
Article Id 414149
Description This article explains the meaning and usage of the timezone_dayst field in FortiWeb event logs.
Scope FortiWeb v7.2.
Solution

timezone_dayst indicates daylight saving time (DST), but it cannot simply be interpreted as a DST offset. Instead, it works in conjunction with the primary timezone setting to calculate the correct timestamp adjustment.

 

Example retrieved from an event log:


[type=event]
date=yyyy-mm-dd time=hh:mm:ss log_id=10000016 msg_id=000000004360 device_id=FVVM02TMxxxxxxxxx eventtime=xxxxxxxxxxxxxxxxxxxxx
vd="root" timezone="(GMT)Greenwich Mean Time: Dublin,Edinburgh,Lisbon,London" timezone_dayst="GMTb+0"
type=event subtype="system" pri=alert trigger_policy="N/A" user=ncsjadmin ui=sshd action=login status=failure msg="User ncsjadmin login failed from ssh(xx.xx.xx.xx)"

 

The timezone_dayst field includes values such as GMTa+7 or GMTc-8. These values do not represent direct DST offsets. Instead, they are internal representations used by FortiWeb to calculate the effective time offset when DST is considered.

 

Examples:


timezone="(GMT-8:00)Pacific Time (US&Canada)", timezone_dayst="GMTa+7"
Calculation: -8 (base timezone) + 7 = -1


Result:

One hour DST offset is applied to the timestamp:


timezone="(GMT+8:00)Kuala Lumpur, Singapore", timezone_dayst="GMTc-8"
Calculation: +8 (base timezone) - 8 = 0


Result:

No DST adjustment is applied.

 

Note:
The timezone_dayst field uses a GMT prefix with an alphabetic suffix (e.g., GMTa, GMTb, GMTc) followed by a numeric value.
These values are used internally by FortiWeb and are not intended to represent standard GMT offsets.

Contributors