Why does availability query not consider "Connection failed" cases as unavailability

[etienneabe]

In the website monitoring application some availability score is calculated as below

sourcetype="web_ping" website_monitoring_search_index title="URL being monitored" | fillnull value=1000 response_code | eval success=case(response_code>=400, 0, timed_out == "True", 0) | fillnull value=1 success | chart count as total, sum(success) as successes | eval availability=round(100(successes/total),2) | fields availability*

However, sometimes unavailability can translate into a connection failing rather than in error codes or timeouts
This may oddly show a site with a hell lot of errors while its availability remains high....

Is this a bug or a deliberate design choice ?
If a design choice, why so ?

[LukeMurphey · Accepted solution]

This is bug. I opened a bug report on it and will fix it very soon in a maintenance release (2.7.2). See https://lukemurphey.net/issues/2316

Update:
I fixed this in version 2.7.2.

[etienneabe]

excellent news. Thanks for your swift reaction.