All Apps and Add-ons

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

etienneabe
New Member

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 ?

Tags (1)
0 Karma
1 Solution

LukeMurphey
Champion

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.

View solution in original post

0 Karma

LukeMurphey
Champion

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.

0 Karma

etienneabe
New Member

excellent news. Thanks for your swift reaction.

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...