config_example.yml

# - - - - - - - - - - - - - - #
# LogRenderer's configuration #
# - - - - - - - - - - - - - - #

# The port the web server will listen to
port: 8080
# The url prefix of the web interface (e.g. `/logrenderer` if the index of the application is `/logrenderer`). You can leave this empty if the index is the root (`/`) of your website
url-prefix: "/logrenderer"
# The url of the website home
website-home-url: "https://www.your-website.net"
# The url of the website logo
website-logo-url: "https://www.your-website.net/storage/img/your-logo.png"
# The url of the website favicon
website-favicon-url: "https://www.your-website.net/storage/img/your-favicon.png"
# Whether debug logs should be printed or not
debug: true
# The delay before a new file watcher is started when a log file is reset/renamed
delay-before-rewatch: "10ms"
# An optional prefix that will be added in front of each log file path,
# for instance when the filesystem is mounted as a volume in a container
path-prefix: ""
# The path of the file containing the logs style rules
style-file-path: "logs-styles.yml"

# All the servers to register for logs watching
servers:
    classic:
        -   server-tag: "serv_1"
            display-name: "Server 1"
            log-file-path: "/path/to/server_1/logs/latest.log"
            syntax-highlighting: &spigot # Anchor this syntax highlighting to re-use it in similar servers
                -   field: "time"
                    # JavaScript-style regular expression to select the part of the log line that should inherit of the above CSS class ('time' in this example)
                    regex: '^\[\d{2}:\d{2}:\d{2}]'
                -   field: "info"
                    regex: '(?<=(^\[\d{2}:\d{2}:\d{2}]) )\[.{0,30}\/INFO]'
                -   field: "warn"
                    regex: '(?<=(^\[\d{2}:\d{2}:\d{2}]) )\[.{0,30}\/WARN]'
                -   field: "error"
                    regex: '(?<=(^\[\d{2}:\d{2}:\d{2}]) )\[.{0,30}\/ERROR]'
                -   field: "content"
                    regex: '(?<=(^\[\d{2}:\d{2}:\d{2}] \[.{0,30}\/(INFO|WARN|ERROR)]: )).*$'
            archived-logs-dir-path: "/path/to/server_1/logs"
            # The archived log reader supports plain text and gzip plain text files
            archived-logs-filename-format: "*.log.gz"
        -   server-tag: "counter"
            display-name: "Counter"
            log-file-path: "~/dir/counter-output.log"
            syntax-highlighting:
                -   field: "text"
                    regex: '.*'
    dynamic:
        -   server-tag: "paper"
            display-name: "Paper %id%"
            # The pattern of the instances log file, it can contain joker characters like '*'
            log-file-pattern: "/path/to/DynamicServers/Paper_*/logs/latest.log"
            # The Golang-style regular expression to extract the instance identifier from the log file path, the name of the group must be 'id'
            instance-identifier: ".*/Paper_(?P<id>\\d*)/logs/latest\\.log"
            syntax-highlighting: *spigot # Re-use of serv_1's syntax highlighting
            # Using '%id%' to include the identifier of the instance identifier
            archived-logs-root-dir: "/path/to/DynamicServers/Paper_%id%/logs"
            # The archived log reader supports plain text and gzip plain text files
            archived-logs-file-pattern: "*.log.gz"