aboutsummaryrefslogtreecommitdiff
path: root/ezau-sample.toml
AgeCommit message (Collapse)Author
2024-08-28add setting for log sortingDaniel Schadt
2024-08-28remove zip functionalityDaniel Schadt
2024-07-30feat: add dps.report upload url configurationnetworkjanitor
2022-01-24feat(im-matrix): added multi-room supportXyoz Netsphere
2021-03-06initial support for matrix log postingDaniel Schadt
Similar to Discord posting, this now allows ezau to post a message to the given Matrix room for every log. The text handling is still pretty bad and should be reworked, but so should the Discord one. This is just the initial support, now that the actual posting works we can add some tests and proper text parsing, together with unifying some of the logic between Discord and Matrix. Note that this currently only works for unencrypted rooms!
2020-08-17add a minimum_duration settingDaniel Schadt
2020-07-20allow zipping to be disabledDaniel Schadt
If you use ezau on Windows, you might prefer to use the built-in zipping functionality from arcDPS instead of relying on ezau to do this job. However, that would lead to weird interactions because arcDPS would still create the temporary file in the watched folder, and powershell would race with ezau to zip and delete this temporary file. To prevent this from breaking existing (& working) configurations - and to stick true to the name - zipping is enabled by default if not given otherwise in the configuration.
2020-07-17retry uploadingDaniel Schadt
As it turns out, uploading is often the reason why the process crashes/exits. This is bad because it means that 1) we lose links to logs (as they are not being uploaded), leading to incomplete reporting and 2) we rely on an external watchdog to keep the service alive (and I'd rather just not have ezau crashing, especially on Windows where we usually don't supervise it with systemd). Therefore, a configuration setting has been added that lets ezau retry the upload process. This is not 100% good and failsafe, because 1) it always waits a hardcoded amount of seconds (instead of e.g. using a proper backoff timer) 2) it blocks the rest of the process, so no logs will be compressed while it is retrying a single log 3) after those retries, the process will still exit But it is a good first approximation, and the aforementioned issues can be fixed "relatively easily" (e.g. by moving the whole per-log logic into a separate thread(pool) and handling failures even better).
2020-06-08add sample configuration as separate fileDaniel Schadt