Portainer Templates logo

Portainer Templates

Loggifly Loggifly

Stack

MonitoringLogs

A Lightweight Tool that monitors Docker Container Logs for predefined keywords or regex patterns and sends Notifications.

Image details

Architecture: amd64, arm64
Image size: 31 MB
User: clemcer

Source details

Repo: clemcer/loggifly
Stars: 2k
Forks: 50
Language: Python
License: MIT
Latest: v2.1.1 · 1 month ago
Updated: 14 days ago
Website: clemcer.github.io/LoggiFly/

Configuration

Type
Compose
Platform
linux
Image
ghcr.io/clemcer/loggifly:latest
Volumes
/var/run/docker.sock : /var/run/docker.sock/config : /portainer/Files/AppData/Config/loggifly/config.yaml
Env vars
TZ=Europe/Athens
Restart
unless-stopped
Source
Repo

Template by xneo1·Source

Standalone Install

Select an install method, to see config/commands for deploying Loggifly

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Loggifly, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

version: "3.8"
services:
  loggifly:
    image: ghcr.io/clemcer/loggifly:latest
    container_name: loggifly
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      # Comment out the following if you are only using environment variables. 
      # A config template will be downloaded in /config
      # edit and rename it to config.yaml or create a new file with your config in it
      - /portainer/Files/AppData/Config/loggifly/config.yaml:/config 
    environment:
      - TZ=Europe/Athens
    restart: unless-stopped

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/loggifly.yml up -d

More install options in our documentation, or see clemcer/loggifly for app-specific guidance.


LoggiFly


<a href="https://clemcer.github.io/loggifly/">Documentation</a>
<a href="https://github.com/clemcer/loggifly/issues">Report Bug</a>
<a href="https://github.com/clemcer/loggifly/issues">Request Feature</a>


LoggiFly - A Lightweight Tool that monitors Docker Container Logs for predefined keywords or regex patterns and sends Notifications.
Get instant alerts for security breaches, system errors, or custom patterns through your favorite notification channels. 🚀
Ideal For:
  • ✅ Catching security breaches (e.g., failed logins in Vaultwarden)
  • ✅ Debugging crashes with attached log context
  • ✅ Restarting containers on specific errors or stopping them completely to avoid restart loops
  • ✅ Monitoring custom app behaviors (e.g., when a user downloads an audiobook on your Audiobookshelf server)

<img src="https://raw.githubusercontent.com/clemcer/loggifly/HEAD/docs/public/vault_failed_login.gif" alt="Failed Vaultwarden Login" width="auto" height="200">

Features

  • 🔍 Plain Text, Regex & Multi-Line Log Detection: Catch simple keywords or complex patterns in log entries that span multiple lines.
  • 🚨 Ntfy/Apprise Alerts: Send notifications directly to Ntfy or via Apprise to 100+ different services (Slack, Discord, Telegram) or even to your own custom endpoint.
  • 🔁 Trigger Stop/Restart: A restart/stop of the monitored container can be triggered on specific critical keywords.
  • 📁 Log Attachments: Automatically include a log file to the notification for context.
  • ⚡ Automatic Reload on Config Change: The program automatically reloads the config.yaml when it detects that the file has been changed.
  • 📝 Configurable Alerts: Filter log lines for relevant information and use templates for your messages and notification titles.
  • 🌐 Remote Hosts: Connect to multiple remote Docker hosts.
  • 🐳 Multi-Platform Support: LoggiFly runs on Docker, Docker Swarm and Podman

Screenshots

collage of screenshots


Customize notifications and filter log lines for relevant information:

Custom Tepmplates Collage

Documentation

Support

If you find LoggiFly useful, drop a ⭐️ on the repo or buy me a coffee!

<a href="https://www.buymeacoffee.com/clemcer" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" alt="Buy Me A Coffee" height="50"></a>
<a href="https://ko-fi.com/clemcer" target="_blank"><img src="https://ko-fi.com/img/githubbutton_sm.svg" alt="Support on Ko-fi" height="50"></a>

Star History

Star History Chart

License

MIT

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/loggifly/config.yaml

Can't reach the Docker socket

loggifly talks to Docker through /var/run/docker.sock. If the logs show "permission denied while trying to connect to the Docker daemon socket", the app's user can't access it.

  • Check the socket exists on the host: ls -l /var/run/docker.sock
  • Run the container as root, or add the docker group's id to the container with group_add.

Image won't pull

Test the pull directly on the host: docker pull ghcr.io/clemcer/loggifly:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Loggifly is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything Loggifly needs bundled into one download. This template pulls ghcr.io/clemcer/loggifly:latest, which Docker fetches once (about 31 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Loggifly's comes from the GitHub Container Registry, published by clemcer.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Volumes

A volume is where Loggifly keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /var/run/docker.sock from /var/run/docker.sock on the host (a socket it talks to, not storage)
  • /config from /portainer/Files/AppData/Config/loggifly/config.yaml on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Loggifly takes 1 of them, all with defaults you can leave alone or tweak:

  • TZ, defaults to Europe/Athens

Restart policy

The restart policy here is unless-stopped, so Docker restarts Loggifly after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Loggifly sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container loggifly. That's what you'll spot in the containers list and use in commands like docker logs loggifly.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

Loggifly is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Loggifly up. Add the template list to Portainer once, then deploying Loggifly is a click rather than a wall of config.