Fix MongoDB plugin early exit on secondary nodes

[A-Henning]

The plugin was unconditionally exiting when connected to secondary MongoDB nodes, causing no piggybacking data generation and the loss off All MongoDB Services on the Dummy Host.

Fix: Only exit if there is truly no primary node available.

---

Expected vs Observed Behavior

Expected: Plugin should generate piggybacking data for MongoDB monitoring services even when connected to secondary nodes, as long as a primary exists in the replica set.

Observed: Plugin exits early with unconditional return statement when connected to secondary nodes, preventing any piggybacking data generation and causing complete loss of all MongoDB Services on the dummy host.

Operating System

Ubuntu 20.04/22.04 LTS (CheckMK agent host)
CheckMK version: 2.4.0p7.cce

Local Setup

• MongoDB Atlas cluster behind Azure Private Endpoint
• Load balancer (managed by mongo) routing connections to secondary MongoDB nodes
• CheckMK agent with mk_mongodb.py plugin for piggybacking

Reproduce (routing is managed by Mongo - so its only reproducable if you are being routed to a secondary node)

1. Set up MongoDB Atlas cluster with Azure Private Endpoint
2. Configure CheckMK mk_mongodb.py plugin to connect via Private Endpoint
3. MongoDB Atlas Load Blancer may route to secondary MongoDB node
4. Plugin exits early on line 985 without generating piggybacking data
5. All MongoDB services disappear from the target dummy host

Root Cause

Line 985 contains return without checking if a primary exists in the replica set.

Solution

Replace unconditional return with conditional logic that only exits if no primary is available.

Changes

• Modified line 985 in agents/plugins/mk_mongodb.py
• Added condition to check for primary existence before returning
• Allows monitoring to continue from secondary nodes when primary is available

Testing

• Tested with MongoDB Atlas behind Azure Private Endpoint
• Verified piggybacking data generation from secondary nodes
• Confirmed all services appear correctly on target hosts

Impact

Fixes MongoDB Atlas monitoring for users with:

• Azure Private Endpoints
• MongoDB Atlas Load balancers routing to secondary nodes
• Any setup where connection lands on secondary first

---

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[A-Henning]

I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA.

[BenediktSeidl]

Thanks for your contribution! I'm trying to fully understand your situation: If i read the code and the comment correctly, the primary node vanishes completely, is this correct? So it's not just that the load balancer switches to another node, but the primary node is removed from the cluster?

[A-Henning]

Thanks for your contribution! I'm trying to fully understand your situation: If i read the code and the comment correctly, the primary node vanishes completely, is this correct? So it's not just that the load balancer switches to another node, but the primary node is removed from the cluster?

The Node does not vanish from the cluster. The Load Balancer switches to a secondary Node which causes the MongoDB Plugin to exit early. It does therefore not generate Piggyback Data for my MongoDB Dummy-Host which results in the loss of all CheckMK Services that this Plugin provides.

[BenediktSeidl]

Thanks for the clarification. We will have an internal discussion about this, and then come back to you.