Recommended MongoDB Agent Configuration Patterns for Foglight MongoDB Monitoring (4381949)

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Recommended MongoDB Agent Configuration Patterns for Foglight MongoDB Monitoring
Description

This KB explains the correct way to configure MongoDB agents in Foglight.

Using the wrong pattern can cause alarms to appear under the wrong agent and MongoDB objects to switch ownership.
Cause

These issues happen when MongoDB agents use duplicate monitoring paths, such as connecting to both mongos and individual shard/config servers. When more than one agent connects to the same cluster through any path, Foglight merges the data and creates churn.
Resolution
Use only one of the two supported patterns:
Option A — Mongos‑Only (Recommended)

Keep only the mongos entries:
```
<mongos>:27017
```
Remove all shard and config entries:
```
<shard>:22000
<config>:20000
```
Option B — Direct Shard/Config Monitoring (Advanced)

Include only shard and config servers:
```
<shard>:22000
<config>:20000
```
Do not include mongos nodes.
Only one agent may monitor these hosts.

Important
- Only one Foglight agent can monitor a MongoDB cluster.
- Do not mix Option A and B for the same cluster.
- Replica set names in MongoDB must be unique within the monitored environment. If two clusters use the same replica set names, Foglight will merge them.
- Clean MongoDB topologies after switching to a clean pattern (as described in Knowledgebase article 4381947 .

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title