LoggiFly

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)

Content

Features
Screenshots
Quick Start
Configuration Deep Dive
Remote Hosts
Docker Swarm
Tips
Support / Buy me a coffee

🚀 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.

🖼 Screenshots

🎯 Customize notifications and filter log lines for relevant information:

Tip

For better security use a Docker Socket Proxy. You won't be able to trigger container stops/restarts with a proxy, but if you don't need that, consider taking a look at this section before you wrap up the Quick Start install and consider using that compose file instead of the basic one.

⚡️ Quick start

In this quickstart only the most essential settings are covered, here is a more detailed config walkthrough.

Choose your preferred setup method - a simple docker compose with environment variables for basic use or a YAML config for advanced control.

Environment variables allow for a simple and much quicker setup
With a config.yaml you can use complex Regex patterns, have different keywords & other settings per container and set keywords that trigger a restart/stop of the container.

Note

In previous versions the default location for the config.yaml file was /app/config.yaml. The old path still works (so not a breaking change) but the new official path is now /config/config.yaml.
LoggiFly will first look in /config/config.yaml, and fall back to /app/config.yaml if it's not found.
When /config is mounted a config template will be downloaded into that directory.

Click to expand: 🐋 Basic Setup: Docker Compose (Environment Variables)

Ideal for quick setup with minimal configuration:

version: "3.8"
services:
  loggifly:
    image: ghcr.io/clemcer/loggifly:latest
    container_name: loggifly
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      # This is where you would put your config.yaml file (ignore if you are only using environment variables)
      # - ./loggifly/config:/config  
    environment:
      # Choose at least one notification service
      NTFY_URL: "https://ntfy.sh"       
      NTFY_TOPIC: "your_topic"          
      # Token or Username+Password In case you need authentication
      # NTFY_TOKEN:
      # NTFY_USERNAME:
      # NTFY_PASSWORD:
      APPRISE_URL: "discord://..."      # Apprise-compatible URL
    
      CONTAINERS: "vaultwarden,audiobookshelf"        # Comma-separated list
      GLOBAL_KEYWORDS: "error,failed login,password"  # Basic keyword monitoring
      GLOBAL_KEYWORDS_WITH_ATTACHMENT: "critical"     # Attaches a log file to the notification
    restart: unless-stopped

Here you can find some more environment variables that you could set.

Click to expand: 📜 Advanced Setup: YAML Configuration

Recommended for granular control, regex patterns and action_keywords:

Step 1: Docker Compose

Use this docker compose and edit this line:

volumes:
  - ./loggifly/config:/config  # 👈 Replace left side of the mapping with your local path

If you want you can configure some of the settings or sensitive values like ntfy tokens or apprise URLs via Environment Variables.

Step 2: Configure Your config.yaml

If /config is mounted a template file will be downloaded into that directory. You can edit the downloaded template file and rename it to config.yaml to use it.
You can also take a look at the Configuration-Deep-Dive for all the configuration options.

Or you can just edit and copy paste the following minimal config into a newly created config.yaml file in the mounted /config directory:

# You have to configure at least one container.
containers:
  container-name:  # Exact container name
  # Configure at least one type of keywords or use global keywords
    keywords:
      - error
      - regex: (username|password).*incorrect  # Use regex patterns when you need them
    # Attach a log file to the notification 
    keywords_with_attachment:
      - warn
    # Caution advised! These keywords will trigger a restart/stop of the container
    # There is an action_cooldown (see config deep dive)
    action_keywords:
      - stop: traceback
      - restart: critical

# Optional. These keywords are being monitored for all configured containers. 
global_keywords:
  keywords:
    - failed
  keywords_with_attachment:
    - critical

notifications:     
  # Configure either Ntfy or Apprise or both
  ntfy:
    url: http://your-ntfy-server  
    topic: loggifly                   
    token: ntfy-token               # Ntfy token in case you need authentication 
    username: john                  # Ntfy Username+Password in case you need authentication 
    password: 1234                  # Ntfy Username+Password in case you need authentication 
  apprise:
    url: "discord://webhook-url"    # Any Apprise-compatible URL (https://github.com/caronc/apprise/wiki)

When everything is configured start the container

docker compose up -d

🤿 Configuration Deep Dive

The Quick Start only covered the essential settings, here is a more detailed walktrough of all the configuration options.

📁 Basic Structure

The config.yaml file is divided into four main sections:

settings: Global settings like cooldowns and log levels. (Optional since they all have default values)
notifications: Ntfy (URL, Topic, Token, Priority and Tags), your Apprise URL and/or a custom webhook url
containers: Define which Containers to monitor and their specific Keywords (plus optional settings).
global_keywords: Keywords that apply to all monitored Containers.

Important

For the program to function you need to configure:

at least one container
at least one notification service (Ntfy, Apprise or custom webhook)
at least one keyword / regex pattern (either set globally or per container)

The rest is optional or has default values.

Here you can find a config template with all available configuration options and explaining comments. When /config is mounted in the volumes section of your docker compose this template file will automatically be downloaded.

Here you can find an example config with some use cases.

⚙️ Settings

These are the default values for the settings:

Click to expand: Settings:

settings:          
  log_level: INFO               # DEBUG, INFO, WARNING, ERROR
  notification_cooldown: 5      # Seconds between alerts for same keyword (per container)
  notification_title: default   # configure a custom template for the notification title (see section below)
  action_cooldown: 300          # Cooldown period (in seconds) before the next container action can be performed. Maximum is always at least 60s.
  attachment_lines: 20          # Number of Lines to include in log attachments
  multi_line_entries: True      # Monitor and catch multi-line log entries instead of going line by line. 
  reload_config: True           # When the config file is changed the program reloads the config
  disable_start_message: False           # Suppress startup notification
  disable_shutdown_message: False        # Suppress shutdown notification
  disable_config_reload_message: False   # Suppress config reload notification
  disable_container_event_message: False # Suppress notification when monitoring of containers start/stop

The setting notification_title requires a more detailed explanation:

Click to expand: notification_title:

When notification_title: default is set LoggiFly uses its own notification titles.
However, if you prefer something simpler or in another language, you can choose your own template for the notification title.
This setting can also be configured per container by the way (see containers section).

These are the two keys that can be inserted into the template:
keywords: The keywords that were found in a log line
container: The name of the container in which the keywords have been found

Here is an example:

notification_title: "The following keywords were found in {container}: {keywords}"

Or keep it simple:

notification_title: {container}

📭 Notifications

You can send notifications either directly to Ntfy or via Apprise to most other notification services.

If you want the data to be sent to your own custom endpoint to integrate it into a custom workflow, you can set a custom webhook URL. LoggiFly will send all data in JSON format.

You can also set all three notification options at the same time

Ntfy:

Click to expand: Ntfy:

notifications:                       
  ntfy:
    url: http://your-ntfy-server    # Required. The URL of your Ntfy instance
    topic: loggifly.                # Required. the topic for Ntfy
    token: ntfy-token               # Ntfy token in case you need authentication 
    username: john                  # Ntfy Username+Password in case you need authentication 
    password: password              # Ntfy Username+Password in case you need authentication 
    priority: 3                     # Ntfy priority (1-5)
    tags: kite,mag                  # Ntfy tags/emojis

Apprise:

Click to expand: Apprise:

notifications:
  apprise:
    url: "discord://webhook-url"    # Any Apprise-compatible URL (https://github.com/caronc/apprise/wiki)

Custom Webhook

Click to expand: Custom Webhook:

notifications:
  webhook: 
    url: https://custom.endpoint.com/post
    # add headers if needed
    headers:
      Authorization: "Bearer token"
      X-Custom-Header": "Test123"

If a webhook is configured LoggiFly will post a JSON to the URL with the following data:

{
  "container": "...",
  "keywords": [...],
  "title": "...",
  "message": "...", 
  "host": "..."   # None unless multiple hosts are monitored
}

🐳 Containers

Here you can define containers and assign keywords, regex patterns, and optional settings to each one.
The container names must match the exact container names you would get with docker ps.

Click to expand: Container Config:

This is how you configure keywords, regex patterns and action_keywords. action_keywords trigger a start/stop of the monitored container:

containers:
  container1:
    keywords:
      - keyword1
      - regex: regex-patern1   # this is how to set regex patterns
    keywords_with_attachment: # attach a logfile to the notification
      - keyword2
      - regex: regex-pattern2
        hide_pattern_in_title: true # Exclude the regex pattern from the notification title for a cleaner look. Useful when using very long regex patterns.
      - keyword3
    action_keywords: # trigger a restart/stop of the container. can not be set globally
      - restart: keyword4
      - stop: 
          regex: regex-pattern3 # this is how to set regex patterns for action_keywords

Some of the settings from the settings section can also be set per container:

containers:
  container2:
    ntfy_tags: closed_lock_with_key   
    ntfy_priority: 5
    ntfy_topic: container3
    attachment_lines: 50
    notification_title: '{keywords} found in {container}'
    notification_cooldown: 2  
    action_cooldown: 60 
  
    keywords:
      - keyword1
      - regex: regex-pattern1

If global_keywords are configured and you don't need additional keywords for a container you can leave it blank:

containers:
  container3:
  container4:

🌍 Global Keywords

When global_keywords are configured all containers are monitored for these keywords:

Click to expand: Global Keywords:

global_keywords:              
  keywords:
    - error
  keywords_with_attachment: # attach a logfile
    - regex: (critical|error)

📝 Customize Notifications (Templates & Log Filtering)

For users who want more control over the appearance of their notifications, there is an option to configure templates and filter log entries to display only the relevant parts.
Here are some examples.
Filtering is most straightforward with logs in JSON Format, but plain text logs can also be parsed by using named groups in the regex pattern.

Note

If you want to modify the notification title take a look at the setting notification_title in the settings section.

Click to expand: Filter Logs and set custom template:

Template for JSON Logs:

json_template only works if the Logs are in JSON Format. Authelia is one such example.
You can only use the placeholder variables that exist as keys in the JSON from the log line you want to catch.

Here is an example where you want to catch this very long log entry from Authelia:

{"level":"error","method":"POST","msg":"Unsuccessful 1FA authentication attempt by user 'example_user' and they are banned until 12:23:00PM on May 1 2025 (+02:00)","path":"/api/firstfactor","remote_ip":"192.168.178.191","stack":[{"File":"github.com/authelia/authelia/v4/internal/handlers/response.go","Line":274,"Name":"doMarkAuthenticationAttemptWithRequest"},{"File":"github.com/authelia/authelia/v4/internal/handlers/response.go","Line":258,"Name":"doMarkAuthenticationAttempt"},{"File":"github.com/authelia/authelia/v4/internal/handlers/handler_firstfactor_password.go","Line":51,"Name":"handlerMain.FirstFactorPasswordPOST.func14"},{"File":"github.com/authelia/authelia/v4/internal/middlewares/bridge.go","Line":66,"Name":"handlerMain.(*BridgeBuilder).Build.func7.1"},{"File":"github.com/authelia/authelia/v4/internal/middlewares/headers.go","Line":65,"Name":"SecurityHeadersCSPNone.func1"},{"File":"github.com/authelia/authelia/v4/internal/middlewares/headers.go","Line":105,"Name":"SecurityHeadersNoStore.func1"},{"File":"github.com/authelia/authelia/v4/internal/middlewares/headers.go","Line":30,"Name":"SecurityHeadersBase.func1"},{"File":"github.com/fasthttp/router@v1.5.4/router.go","Line":441,"Name":"(*Router).Handler"},{"File":"github.com/authelia/authelia/v4/internal/middlewares/log_request.go","Line":14,"Name":"handlerMain.LogRequest.func31"},{"File":"github.com/authelia/authelia/v4/internal/middlewares/errors.go","Line":38,"Name":"RecoverPanic.func1"},{"File":"github.com/valyala/fasthttp@v1.59.0/server.go","Line":2380,"Name":"(*Server).serveConn"},{"File":"github.com/valyala/fasthttp@v1.59.0/workerpool.go","Line":225,"Name":"(*workerPool).workerFunc"},{"File":"github.com/valyala/fasthttp@v1.59.0/workerpool.go","Line":197,"Name":"(*workerPool).getCh.func1"},{"File":"runtime/asm_amd64.s","Line":1700,"Name":"goexit"}],"time":"2025-05-01T14:19:29+02:00"}

In the config.yaml you can set a json_template for both plain text keywords and regex patterns. In the template I inserted three keys from the JSON Log Entry:

containers:
  authelia:
    keywords:
      - keyword: Unsuccessful 1FA authentication
        json_template: '🚨 Failed Login Attempt:\n{msg}\n🔎 IP: {remote_ip}\n🕐{time}' 
      - regex: Unsuccessful.*authentication
        json_template: '🚨 Failed Login Attempt:\n{msg}\n🔎 IP: {remote_ip}\n🕐{time}'

Template using named capturing groups in Regex Pattern:

To filter non JSON Log Lines for certain parts you have to use a regex pattern with named capturing groups.
Lets take (?P<group_name>...) as an example. P<group_name> assigns the name group_name to the group. The part inside the parentheses (...) is the pattern to match.
Then you can insert the {group_name} into your custom message template.

Example Log Line from audiobookshelf:

[2025-05-03 10:16:53.154] INFO: [SocketAuthority] Socket VKrcSNa--FjwAqmSAAAU disconnected from client "example user" after 11696ms (Reason: transport close)

Regex pattern & Template:

containers:
  audiobookshelf:
    keywords:
      - regex: '(?P<timestamp>\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}.\d{3}).*Socket.*disconnected from client "(?P<user>[A-Za-z\s]+)"'
        template: '\n🔎 The user {user} was seen!\n🕐 {timestamp}'
        hide_pattern_in_title: true  # Exclude the regex pattern from the notification title for a cleaner look

Result:

with template and hide_pattern_in_title:

without for comparison:

Add original Log Entry to template:

WIth both json_template and template you can add the key original_log_line to your template to add the full log entry to your notification message.

🍀 Environment Variables

Except for action_keywords, container specific settings/keywords and regex patterns you can configure most settings via Docker environment variables.

Click to expand: Environment Variables

Variables	Description	Default
`NTFY_URL`	URL of your Ntfy server instance	N/A
`NTFY_TOKEN`	Authentication token for Ntfy in case you need authentication.	N/A
`NTFY_USERNAME`	Ntfy Username to use with the password in case you need authentication.	N/A
`NTFY_PASSWORD`	Ntfy password to use with the username in case you need authentication.	N/A
`NTFY_TOPIC`	Notification topic for Ntfy.	N/A
`NTFY_TAGS`	Tags/Emojis for ntfy notifications.	kite,mag
`NTFY_PRIORITY`	Notification priority for ntfy messages.	3 / default
`APPRISE_URL`	Any Apprise-compatible URL	N/A
`CONTAINERS`	A comma separated list of containers. These are added to the containers from the config.yaml (if you are using one).	N/A
`SWARM_SERVICES`	A comma separated list of docker swarm services to monitor.	N/A
`LOGGIFLY_MODE`	Set this variable to `swarm` when wanting to use LoggiFly in swarm mode	N/A
`GLOBAL_KEYWORDS`	Keywords that will be monitored for all containers. Overrides `global_keywords.keywords` from the config.yaml.	N/A
`GLOBAL_KEYWORDS_WITH_ATTACHMENT`	Notifications triggered by these global keywords have a logfile attached. Overrides `global_keywords.keywords_with_attachment` from the config.yaml.	N/A
`NOTIFICATION_COOLDOWN`	Cooldown period (in seconds) per container per keyword before a new message can be sent	5
`ACTION_COOLDOWN`	Cooldown period (in seconds) before the next container action can be performed. Always at least 60s. (`action_keywords` are only configurable in YAML)	300
`LOG_LEVEL`	Log Level for LoggiFly container logs.	INFO
`MULTI_LINE_ENTRIES`	When enabled the program tries to catch log entries that span multiple lines. If you encounter bugs or you simply don't need it you can disable it.	True
`ATTACHMENT_LINES`	Define the number of Log Lines in the attachment file	20
`RELOAD_CONFIG`	When the config file is changed the program reloads the config	True
`DISBLE_START_MESSAGE`	Disable startup message.	False
`DISBLE_SHUTDOWN_MESSAGE`	Disable shutdown message.	False
`DISABLE_CONFIG_RELOAD_MESSAGE`	Disable message when the config file is reloaded.	False
`DISABLE_CONTAINER_EVENT_MESSAGE`	Disable message when the monitoring of a container stops or starts.	False

📡 Remote Hosts

LoggiFly supports connecting to multiple remote hosts.
Remote hosts can be configured by providing a comma-separated list of addresses in the DOCKER_HOST environment variable.
To use TLS you have to mount /certs in the volumes section of your docker compose.
LoggiFly expects the TLS certificates to be in /certs/{ca,cert,key}.pem or in case of multiple hosts /certs/{host}/{ca,cert,key}.pem with {host} being either the IP or FQDN.
You can also combine remote hosts with a mounted docker socket.

Note

When the connection to a docker host is lost, LoggiFly will try to reconnect every 60s

Labels

When multiple hosts are set LoggiFly will use labels to differentiate between them both in notifications and in logging.
You can set a label by appending it to the address with "|" (see example).
When no label is set LoggiFly will use the hostname retrieved via the docker daemon. If that fails, usually because INFO=1 has to be set when using a proxy, the labels will just be Host-{Nr}.

If you want to set a label to the mounted docker socket you can do so by adding unix:///var/run/docker.sock|label in the DOCKER_HOST environment variable (the socket still has to be mounted) or just set the address of a socket proxy with a label.

Remote Hosts Example

In this example, LoggiFly monitors container logs from the local host via a mounted Docker socket, as well as from two remote Docker hosts configured with TLS. One of the remote hosts is referred to as ‘foobar’. The local host and the second remote host have no custom label and are identified by their respective hostnames.

Click to expand: Remote Hosts: Docker Compose

version: "3.8"
services:
  loggifly:
    image: ghcr.io/clemcer/loggifly:latest
    container_name: loggifly 
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./loggifly/config:/config # Place your config.yaml here if you are using one
      - ./certs:/certs
      # Assuming the Docker hosts use TLS, the folder structure for the certificates should be like this:
      # /certs/
      # ├── 192.168.178.80/
      # │   ├── ca.pem
      # │   ├── cert.pem
      # │   └── key.pem
      # └── 192.168.178.81/
      #     ├── ca.pem
      #     ├── cert.pem
      #     └── key.pem
    environment:
      TZ: Europe/Berlin
      DOCKER_HOST: tcp://192.168.178.80:2376,tcp://192.168.178.81:2376|foobar
    restart: unless-stopped

Socket Proxy

You can also connect via a Docker Socket Proxy.
A Socket Proxy adds a security layer by controlling access to the Docker daemon, essentially letting LoggiFly only read certain info like container logs without giving it full control over the docker socket.
With the linuxserver image I have had some connection and timeout problems so the recommended proxy is Tecnativa/docker-socket-proxy.
When using the Tecnativa Proxy the log stream connection drops every ~10 minutes for whatever reason, LoggiFly simply resets the connection.

Here is a sample docker compose file:

Click to expand: Socket Proxy: Docker Compose

version: "3.8"
services:
  loggifly:
    image: ghcr.io/clemcer/loggifly:latest
    container_name: loggifly 
    volumes:
      - ./loggifly/config:/config # Place your config.yaml here if you are using one
    environment:
      TZ: Europe/Berlin
      DOCKER_HOST: tcp://socket-proxy:2375
    depends_on:
      - socket-proxy
    restart: unless-stopped
    
  socket-proxy:
    image: tecnativa/docker-socket-proxy
    container_name: docker-socket-proxy
    environment:
      - CONTAINERS=1  
      - POST=0        
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro  
    restart: unless-stopped

Note

action_keywords don't work when using a socket proxy.

Docker Swarm (Experimental)

Important

Docker Swarm Support is still experimental because I have little to no experience with it and can not say for certain whether it works flawlessly. If you notice any bugs or have suggestions let me know.

To use LoggiFly in swarm mode you have to set the environment variable LOGGIFLY_MODE to swarm.

The config.yaml is passed to each worker via Docker Configs (see example).

The configuration pretty much stays the same except that you set swarm_services instead of containers or use the SWARM_SERVICES environment variable.

If normal containers are set instead of or additionally to swarm_services LoggiFly will also look for these containers on every node.

Docker Compose

Click to expand: Docker Compose

version: "3.8"

services:
  loggifly:
    image: ghcr.io/clemcer/loggifly:latest
    deploy:
      mode: global  # runs on every node
      restart_policy:
        condition: any
        delay: 5s
        max_attempts: 5
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro 
    environment:
      TZ: Europe/Berlin
      LOGGIFLY_MODE: swarm
      # Uncomment the next three variables if you want to only use environment variables instead of a config.yaml
      # SWARM_SERVICES: nginx,redis
      # GLOBAL_KEYWORDS: keyword1,keyword2
      # GLOBAL_KEYWORDS_WITH_ATTACHMENT: keyword3
      # For more environment variables see the environment variables section in the README 
# Comment out the rest of this file if you are only using environment variables
    configs:
      - source: loggifly-config
        target: /config/config.yaml  

configs:
  loggifly-config:
    file: ./loggifly/config.yaml  # SET YOU THE PATH TO YOUR CONFIG.YAML HERE

Config.yaml

Click to expand: config.yaml

In the config.yaml you can set services that should be monitored just like you would do with containers.

swarm_services:
  nginx:
    keywords:
      - error
  redis:
    keywords_with_attachment:
      - fatal

If both nginx and redis are part of the same compose stack named my_service you can configure that service name to monitor both:

swarm_services:
  my_service: # includes my_service_nginx and my_service_redis
    keywords:
      - error
    keywords_with_attachment:
      - fatal

For all available configuration options, refer to the Containers section of the configuration walkthrough — the swarm_services configuration is identical to that of containers.

💡 Tips

Ensure containers names exactly match your Docker container names.
- Find out your containers names: docker ps --format "{{.Names}}"
- 💡 Pro Tip: Define the container_name: in your compose files.
action_keywords can not be set via environment variables, they can only be set per container in the config.yaml. The action_cooldown is always at least 60s long and defaults to 300s
Regex Patterns:
- Validate patterns at regex101.com before adding them to your config.
- use hide_pattern_in_title: true when using very long regex patterns to have a cleaner notification title (or hide found keywords from the title altogether with your own custom notification_title (see settings)
Troubleshooting Multi-Line Log Entries. If LoggiFly only catches single lines from log entries that span over multiple lines:
- Wait for Patterns: LoggiFly needs to process a few lines in order to detect the pattern the log entries start with (e.g. timestamps/log level)
- Unrecognized Patterns: If issues persist, open an issue and share the affected log samples

Name		Name	Last commit message	Last commit date
Latest commit History 202 Commits
app		app
images		images
.gitignore		.gitignore
Dockerfile		Dockerfile
LICENSE		LICENSE
README.md		README.md
config_example.yaml		config_example.yaml
config_template.yaml		config_template.yaml
docker-compose.yaml		docker-compose.yaml
entrypoint.sh		entrypoint.sh
requirements.txt		requirements.txt

License

clemcer/loggifly

Folders and files

Latest commit

History

Repository files navigation

LoggiFly

Content

🚀 Features

🖼 Screenshots

🎯 Customize notifications and filter log lines for relevant information:

⚡️ Quick start

🤿 Configuration Deep Dive

📁 Basic Structure

⚙️ Settings

📭 Notifications

Ntfy:

Apprise:

Custom Webhook

🐳 Containers

🌍 Global Keywords

📝 Customize Notifications (Templates & Log Filtering)

Template for JSON Logs:

Template using named capturing groups in Regex Pattern:

Add original Log Entry to template:

🍀 Environment Variables

📡 Remote Hosts

Labels

Remote Hosts Example

Socket Proxy

Docker Swarm (Experimental)

💡 Tips

Support

Star History

License

About

Topics

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases 11

Packages 0

Uh oh!

Uh oh!

Contributors 3

Languages

Packages