You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two VPSs, on VPS1 I have a couple of websites, and on VPS2 I have netdata installed and Http Check configured to monitor the websites hosted on VPS1. Netdata is reporting response times of around 4000 ms (very long) for the web while, if I use curl from the VPS2 itself to measure response times, it returns around 350 ms which is expected.
@ilyam8 thanks for your answer and help. I have just tested using httpstat and I'm still getting really high response times in comparison. For example, the site https://daxslab.com using httpstat is reporting ~400 ms, but netdata values are around 2000 ms, with peaks of 4000+ (all measurements taken from the same server)
Bug report summary
I have two VPSs, on VPS1 I have a couple of websites, and on VPS2 I have netdata installed and Http Check configured to monitor the websites hosted on VPS1. Netdata is reporting response times of around 4000 ms (very long) for the web while, if I use curl from the VPS2 itself to measure response times, it returns around 350 ms which is expected.
OS / Environment
Netdata version
netdata v1.28.0-47-nightly
Component Name
collectors
Steps To Reproduce
./edit-config go.d/httpcheck.conf
./edit-config go.d/httpcheck.conf
the lines:(around 350 ms in my website)
Expected behavior
Netdata HTTP Response Time and curl response time are expected to be similar.
The text was updated successfully, but these errors were encountered: