LoggiFly

Appearance

Actions ​

Container Actions ​

You can configure container actions to be triggered when a keyword/regex is found in the logs or a container event occurs. Supported actions are restart, stop and start.

You can perform these actions on the monitored container itself or on other containers.

The action_cooldown is per action per container and defaults to 300 seconds (5 minutes) and has to be at least 10 seconds.

INFO

Note that actions require access to the docker socket and generally don't work with a Docker Socket Proxy.

Perform actions on the monitored container ​

yaml
containers:
  action_cooldown: 60  # 1 minute cooldown
  container3:
    # Act on log matches
    - regex: "process.*(failed|did not finish)" 
      action: restart  # Restart the container when this regex is found
    - keyword: critical
      action: stop     # Stop the container when this keyword is found
      action_cooldown: 10  # 10 seconds cooldown for this action

    # Act on container events
    - event: crash
      action: restart
      message_template: '{action_result_message}'

Perform actions on other containers ​

yaml
containers:
  container3:
    - regex: "process.*(failed|did not finish)" 
      action: restart@some-other-container  # Restart another container when this regex is found
    - keyword: critical
      action: stop@some-other-container     # Stop anoter container when this keyword is found
    - keyword: timeout
      action: start@some-other-container

Trigger OliveTin Actions ​

OliveTin is a great tool that allows you to perform predefined commands from a web interface. Fortunately for us it also has a API that we can use to trigger actions when LoggiFly finds certain keywords in the logs.

LoggiFly will send the execution output of the action in a separate notification.

You can configure your OliveTin URL globally in the settings section or per container and even per keyword/regex in case you want to trigger commands on different OliveTin instances.

If you have configured a Local User Login you can configure username and password to trigger actions that require authentication (also in settings, per container and per keyword/regex).

Configuring one simple action ​

Simply configure the olivetin_action_id per keyword or regex.

Here is a an example config snippet:

yaml
containers:
  container3:
    - regex: 'download.*failed'
      olivetin_action_id: some-action-id

settings:
  olivetin_url: http://192.168.178.20:1337
  olivetin_username: admin
  olivetin_password: password

Configuring multiple actions with Arguments ​

You can configure multiple actions and pass arguments by using the olivetin_actions field.

yaml
containers:
  container3:
    - keyword: critical
      olivetin_actions:
        - id: some-action-id
          arguments:
            - name: arg1
              value: value1
            - name: arg2
              value: value2
        - id: some-other-action-id
          arguments:
            - name: arg3
              value: value3
            - name: arg4
              value: value4