10 Dec 2019 11:43 AM - last edited on 18 May 2021 12:44 AM by MaciejNeumann
Can somebody clarify what, exactly, the “failed database connects” metric referenced in the “Detect failed database connects” problem detection rule represents? In a problem card that was opened via this rule, the “Metric anomaly detected” lists “Service connection failures fraction”. I am not clear, what this metric represents… what exactly is the problem detection based on? I presume its a failure in the call to whatever framework is being used in the monitored code to establish a connection to a DB... but I want to make sure that this is a correct understanding... the reference to a "service connection failures fraction" makes me question whether I have the correct understanding.
Solved! Go to Solution.
You are right. Each time when framework responsible for connection acquisition is not able to establish connection before transaction, you have this metric violation.