Fortinet white logo
Fortinet white logo

Administration Guide

Server Latency Event Logging (7.6.5)

Server Latency Event Logging (7.6.5)

FortiWeb 7.6.5 adds a new CLI option to monitor backend latency and log performance issues on a per-policy basis. When the combined server RTT and application response time exceeds a user-defined threshold, FortiWeb logs an event once per minute.

This log can be integrated with an automation stitch to trigger alerts—such as email notifications—when degraded application performance is detected.

CLI Configuration:
config server-policy policy
    edit <policy_name>
        set server-latency-alert <integer>

Sets the server latency threshold in milliseconds (range: 0–65000). If the average latency across the last 15 makconnections exceeds this threshold, FortiWeb generates an event log once per minute. A value of 0 disables this check.

Latency includes server RTT and application response time, and is updated only when new traffic is processed. To avoid redundant logs, FortiWeb logs an event only if the latency was updated and still exceeds the threshold since the last check.

Example Event Log:

Server Latency Event Logging (7.6.5)

Server Latency Event Logging (7.6.5)

FortiWeb 7.6.5 adds a new CLI option to monitor backend latency and log performance issues on a per-policy basis. When the combined server RTT and application response time exceeds a user-defined threshold, FortiWeb logs an event once per minute.

This log can be integrated with an automation stitch to trigger alerts—such as email notifications—when degraded application performance is detected.

CLI Configuration:
config server-policy policy
    edit <policy_name>
        set server-latency-alert <integer>

Sets the server latency threshold in milliseconds (range: 0–65000). If the average latency across the last 15 makconnections exceeds this threshold, FortiWeb generates an event log once per minute. A value of 0 disables this check.

Latency includes server RTT and application response time, and is updated only when new traffic is processed. To avoid redundant logs, FortiWeb logs an event only if the latency was updated and still exceeds the threshold since the last check.

Example Event Log: