search cancel

What mongodb_monitor metric controls the alarm severity when a mongod service is stopped on any slave?

book

Article ID: 255840

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)

Issue/Introduction

We have deployed the mongodb_monitor probe on all the cluster nodes and the probe config is unique across all of them. When the mongod service is stopped on any slave, we are getting the alert (* is not running on this node").

Is there a metric that controls the alarm severity or is this a built it alarm that cannot be changed?

Environment

mongodb_monitor 2.11T3

Resolution

There is no metric defined for (* is not running on this node") as this is a built in alarm that is not customizable