Recommended values for SLA Targets in Fortinet Performance SLA ?

[R_007]

We would like to enable and define the SLA Targets option in 'Performance SLA' section of the SD-WAN configuration in Fortinet console. We are having Fortinet version 7.2.11 as part of FortiGate device.

In our environment, most of the traffic is normal internet browsing , emails and net searches. We do have around 2-3% of traffic to our WFH Windows Servers. We use Microsoft Teams ( free) version for internal communications, which is not self hosted. Further, there is no 'business critical' application such as VOIP or such real-time traffic. We don't have VPN or Proxy network.
Therefore, considering the above factors in mind, we would like to know whether these Latency threshold, Jitter threshold and Packet-Loss threshold mentioned below would be okay for our use cases  ( 250 ms,  55 ms and 1% ) ?

These values were taken from 'Defining WAN performance SLA' section of the official document found here.

As per online searches, the recommended values lie between or around these figures:
50ms-100ms , 20ms-50ms, 1%-3% respectively, for
Latency threshold, Jitter threshold and Packet-Loss threshold.

We seek this advice because the default values in Fortinet console are 5ms, 5ms and 0% , which definitely does not look production graded or realistic and seem very theoretical.

Thanks

[rulasgo3]

Based on your configuration there, it looks like its a straight up/down. if you get 10 ping failures in a row, line is down. if the line is in the "down state" and you get 10 successful pings, line is up again.

your device considers a "lost ping" any ping that takes longer than 500 ms to return.

if you want to put more specific rules in, you can use the SLA target which will allow you to put in a more nuanced approach, instead of it just being ping fail/succeed that determines your link state, you can monitor latency, jitter and packet loss as a percentage to determine if any of those values as measured exceed what you have defined, then the links are considered down.

[R_007]

Thanks for the response, @rulasgo3 . However we are looking for suggestions or some sort of technical advice on what values need to be provided for the three. 

'you can monitor latency, jitter and packet loss as a percentage to determine if any of those values as measured exceed what you have defined, then the links are considered down.'   -  We might have to do the same, but pointers towards any recommended values would help.