So, last weekend, we had a huge conference call because
two Production HTTPS URL's that we monitor with Hobbit were
getting timeouts exceeding 30 seconds.
No other URL's on the Hobbit Server that we monitor were
getting any types of timeouts.
I have two Hobbit Servers, located at two physical sites, Production
& Development. The Production Hobbit Server said that no timeouts
occurred on the two HTTPS URL's. However, the Development Hobbit
Server (which is the primary monitoring server), indicated that the URL's
were timing out.
So, the only difference appeared to be in the network. However, our
network team looked at the network and showed no latency, and
the placed a sniffer on the Development Hobbit Server and saw all
HTTPS packets coming back without timeouts.
Early this week, we placed a box that sniffs that network and can monitor
for specific events. In this case, it's connected to the same network as
the Development Hobbit Server, and its monitoring the HTTPS request
to the two URL's.
Last night, I received timeouts from Hobbit on the URLs, but the sniffer
showed not such timeouts.
I've checked the Hobbit server, CPU, Load, Network, all the graphs don't
show any correlation to the timeouts.
Does anyone have any ideas on this puzzle?
Thanks..James