← Directory

Monocker

Monocker monitors the state of your Docker containers and sends an alert whenever a container starts, stops, pauses, or exits.

  • Infrastructure
  • Monitoring & Logging
  • Tools & Utilities
Monocker monitors the state of your Docker containers and sends an alert whenever a container starts, stops, pauses, or exits. It lets you include or exclude specific containers and optionally limit alerts to paused, exited, unhealthy, or dead states. Notifications can be delivered through Telegram, Pushbullet, Pushover, Discord, Ntfy, Slack, Gotify, Matrix, or Apprise. It is a lightweight, self-hosted option for homelabbers who want simple container status alerts without running a full monitoring stack.

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

23/100 Low

Maintained
2last commit 709 days ago
Popular
46202 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 12 days ago

GitHub stars
202
Open issues
32
Last commit
2024-11-05
Activity
stale

Checked 7 days ago - source: GitHub (petersem/monocker)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 16 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Messaging platform configuration Configure your chosen message platform using the documented credential format: pushbullet@your_api_key@your_device_id, pushover@your_user_key@your_app_api_token, discord@webhook_url, ntfy@topic_title, slack@bot_user_oauth_token@your_chat_id, gotify@server_url@app_token, telegram@your_bot_id@your_chat_id, matrix@server_url@userid@access-token@room-id (userid without the leading @ sign), or apprise@ source

Fetched 8 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I reduce Monocker alerts when containers frequently change state?

Set ONLY_OFFLINE_STATES to true so Monocker only alerts when a container becomes paused, exited, running (unhealthy), or dead. Set EXCLUDE_EXITED to true if you do not want exited containers included at all.

Can Monocker monitor a Docker daemon on another host?

Set DOCKER_HOST to a unix socket, Windows named pipe, or TCP connection. Mount the socket or pipe as a volume if you use a local path, and ensure a proxied Docker endpoint allows GET requests on /containers.

How do I point Monocker at a custom ntfy server?

Use ntfy@topic_title in MESSAGE_PLATFORM and provide CUSTOM_NTFY_SERVER, NTFY_USER, and NTFY_PASS for the custom ntfy server. These options are shown in the Monocker deployment example.

Can one Monocker instance send alerts to multiple message platforms?

No, MESSAGE_PLATFORM accepts only one messaging platform. Run separate Monocker instances for different platforms and use SERVER_LABEL or SERVER_AVATAR to identify which server sent each message.

How can I include the container ID in Monocker notifications?

Set SHA to true. This includes the container SHA ID in the messages sent by Monocker.

Answers sourced from github.com

Community

Collected 16 days ago - public community threads