Latency Issues

If you notice a delay when loading Zenduty, please follow the steps outlined below to troubleshoot the issue and identify the underlying cause. These steps will help you determine if the problem is related to network issues, browser settings, or other factors that could affect the platform's performance.

Please check the speed on the device by using speedtest.net to ensure there is no internet speed issue.

If the issue persists, check if others in your organization are experiencing the same problem. If they aren’t, try accessing Zenduty in an incognito tab to rule out any cache or cookie issues with your browser.

For mobile application slowness, compare it with the web application to determine if it’s specific to mobile. Also, ensure your mobile app is updated to the latest version.

If you're using Zenduty behind a VPN, ensure that your network administrator has whitelisted our IPs and domain to avoid delays that could lead to a server timeout (Error 408). Once the domain and IPs are white-listed, and if you still face latency issues, check your firewall rules. Firewall rules work differently for GET and non-GET [POST] requests, please make sure to check the rules and avoid any discrepancy for the network traffic that flows through the firewall to zenduty servers. 

Strict firewall or security settings can interfere with the communication between your browser and the server. This can result in a request timeout if the server’s response is blocked or delayed.

If there are any discrepancies in the network connection like a slow connection, the Zenduty server will respond with a 408 HTTP status code. Please check internet speed while connecting to https://www.zenduty.com and https://events.zenduty.com.

Command to check the speed.

For GET requests:

curl -s -i https://www.zenduty.com/api/account/ -o /dev/null -w '\nWebsite Response Time for: %{url_effective}\n\nLookup Time:\t\t%{time_namelookup}\nConnect Time:\t\t%{time_connect}\nPre-transfer Time:\t%{time_pretransfer}\nStart-transfer Time:\t%{time_starttransfer}\n\nTotal Time:\t\t%{time_total}\n'

Website Response Time for: https://www.zenduty.com/api/account/

Lookup Time:   	 0.005132
Connect Time:   	 0.236038
Pre-transfer Time:    0.472607
Start-transfer Time:    0.710834

Total Time:   	 0.710840

For Non-GET requests:

curl -s -i -X POST https://events.zenduty.com/api/events/[integration-key]/ -H 'Content-Type: application/json' -d '{"alert_type":"critical", "message":"Some message", "summary":"some summary", "entity_id":"some_entity_id"}' -w '\nWebsite Response Time for: %{url_effective}\n\nLookup Time:\t\t%{time_namelookup}\nConnect Time:\t\t%{time_connect}\nPre-transfer Time:\t%{time_pretransfer}\nStart-transfer Time:\t%{time_starttransfer}\n\nTotal Time:\t\t%{time_total}\n'

Website Response Time for: https://events.zenduty.com/api/events/[integration-key]/

Lookup Time:   	 0.005226
Connect Time:   	 0.221293
Pre-transfer Time:    0.441410
Start-transfer Time:    1.201653

Total Time:   	 1.201717

Proxy:

If a proxy server is used to connect to the internet, misconfigured settings or connection problems with the proxy server can cause a 408 error. The proxy server may fail to establish a timely connection with the zenduty server, resulting in a timeout.

Generic Considerations:

• While making the POST requests, ensure, that payload data do not exceed 800 KB [kilobyte].
• Avoid using fancy characters like emojis or special characters while naming the entities in zenduty like the services, teams, integrations, rules, users,please get in touch with us and others that require text.
• Respect the rate limits while sending the requests to the endpoints. 

Ref: https://www.zenduty.com/docs/rate-limits/

If everything checks out and you're still facing issues, please get in touch with us at support@zenduty.com or via chat with the HAR file from your browser, and a screenshot of your speed test, and our support team will be happy to assist.