DumbMonit

ИнтеграцииБазы данных и очереди сообщений

Мониторинг MongoDB в DumbMonit

The document database itself: replica set members and lag, a missing primary, connections against the limit, WiredTiger cache and assertions.

ДокументацияОфициальный сайт: MongoDB

Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.

Что проверяет DumbMonit

The document database itself: the replica set (members, their state, a missing primary, how far each secondary is behind), connections against the limit, the WiredTiger cache, operations and assertions.

Типичное применение. Document database: replica set, lag, connections, WiredTiger cache

Примеры

  • MongoDB replica set
  • Standalone mongod
  • The database behind UniFi or Rocket.Chat

Как подключается

Что понадобится

  • Username / passwordAn account with the clusterMonitor role only, logged in with SCRAM-SHA-256.

Учётная запись не нужна.

Сетевые порты, которые нужно открыть

  • 27017/TCPMongoDB protocol (default port, plain or TLS)
Шаги настройки: Create a read-only MongoDB account
  1. In mongosh, create the account with the clusterMonitor role.

    use admin
    db.createUser({user: "dumbmonit", pwd: passwordPrompt(), roles: [{role: "clusterMonitor", db: "admin"}]})
  2. In DumbMonit, enter the address of one mongod, for example db1.lan:27018, then the user and its password.

  3. In a replica set, add every member as its own monitor.

  4. Tick TLS if the server requires it.

Обратите внимание. A mongodb+srv:// address is not resolved (enter each member's host), and MongoDB older than 3.6 and mongos routers are not supported.