DumbMonit

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

Мониторинг Redis / Valkey в DumbMonit

The in-memory store itself: memory against maxmemory, refused connections, replication link and lag, failed saves and keyspace size.

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

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

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

The in-memory store itself: memory against maxmemory, refused connections, the replication link and the lag of each replica, failed snapshots and append-only file writes, and the size of the keyspace.

Типичное применение. In-memory store: memory against maxmemory, replication, persistence, keys

Примеры

  • Redis
  • Valkey
  • The cache behind Nextcloud, Immich or Authentik

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

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

  • ACL user (recommended)A Redis user allowed to run INFO and PING only. Sent as AUTH user password.
  • Password onlyFor Redis 5 or older, or a server with only requirepass set. Sent as AUTH password.

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

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

  • 6379/TCPRedis protocol (default port, plain or TLS)
Шаги настройки: Create a read-only Redis user
  1. In redis-cli, create the user (Redis 6 or later, or Valkey).

    ACL SETUSER dumbmonit on >a-long-password -@all +info +ping
  2. Save it: ACL SAVE if the server uses an aclfile, CONFIG REWRITE otherwise.

    ACL SAVE
  3. In DumbMonit, enter the server address, for example cache.lan:6380, then the user and its password.

  4. Tick TLS if the server only accepts TLS on that port (tls-port).

Обратите внимание. On Redis 5 or older, or with only requirepass set, pick Password only: that password carries every right.