NPM pkt loss and response time graph shows 100% pkt loss, but still showing 3ms response time

Question

We're running platform 2019.2.   I had a server which was down, but did not alert.  When I looked back at the response time and packet loss graph, it showed 100% packet loss, but yet 3ms response time.  How is this possible?  I thought with 100% packet loss, my response time would be infinite.   What am I mis-understanding?  The graph is below:

Thanks

mesverrum · Answer

On that note, vote it up
https://thwack.solarwinds.com/t5/NPM-Feature-Requests/Change-Perfstack-chart-behavior-for-missing-data/idi-p/557248

saw10 · Answer

This may be a totally off the mark statement but I would have thought that with 100% packet loss that the response time should have gone to 0 (zero) or shown a gap.  If someone was to look at this image it does not make sense.  I think is a poor representation of what is happening in the environment.

mesverrum · Answer

The new charts don't show data gaps. It's just drawing a straight line from the previous response time before it went down to the new response time after it comes up.