Skip to content
This repository was archived by the owner on Dec 20, 2023. It is now read-only.
This repository was archived by the owner on Dec 20, 2023. It is now read-only.

Monitoring config issue #15

@dustinsmith1024

Description

@dustinsmith1024

When monitoring the config files, it seems nesting is broken on reload.

Example with 2 logging appenders. Sentry will only go on WARN the first time through, but after any change to the config file it starts to run on DEBUG.

"patio": {
                "level": "DEBUG",
                "appenders": [
                    {
                        "type": "ConsoleAppender",
                        "pattern": "{hostname}::{gid}::{pid}::[{[yyyy-MM-ddTHH:mm:ss:SSS (z)]timeStamp}]::{name}::{levelName} - {message}"
                    },
                    {
                        "type": "SentryAppender",
                        "level": "WARN",
                        "pattern": "{message}"
                    }
                ]

            },

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions