Tags: tazjin/journaldriver.bak
Tags
Version 1.1.0 This release of `journaldriver` includes the following features and fixes: * `journaldriver` now correctly recognises and forwards journald's [log priorities][]. Thanks to @ttencate for suggesting and implementing this feature! * `journaldriver` now deals with potential issues while writing the cursor file better than in the previous version. See [issue #2][] for more information. * The previous `CURSOR_POSITION_FILE` environment variable has been replaced with `CURSOR_POSITION_DIR`, which is expected to point at a writable directory in which cursor positions are persisted. This option was previously undocumented and is not used by the NixOS module. The defaults have not changed, so in setups that previously did not customize this option nothing needs to be done. * `journaldriver` depends on significantly fewer Rust libraries now due to a move to a more lightweight HTTP client ([ureq][]) In order to make use of `journald`-priorities applications submitting messages into the journal must add severity information. The easiest way to do this is to use [priority prefixes][]. Please consult the [README][] for additional information. In other news, `journaldriver` is now included in NixOS 18.09 and can be enabled via `services.journaldriver.enable = true;`. Note that as of the time of this release, the version included in NixOS is `v1.0.0`. [log priorities]: http://0pointer.de/public/systemd-man/sd-daemon.html [issue #2]: https://github.com/tazjin/journaldriver/issues/2 [ureq]: https://docs.rs/ureq/ [priority prefixes]: http://0pointer.de/public/systemd-man/sd-daemon.html [README]: https://github.com/tazjin/journaldriver#log-levels--severities--priorities
refactor: Require directory instead of file path for cursors The previous change, which makes journaldriver write the cursor position in two steps, requires that journaldriver can write files adjacent to the cursor position file itself. Instead of simply guessing that this is possible (e.g. by changing the file suffix), expect the user to provide a directory that journaldriver can work with.
chore: Bump version to 1.1.0 ... in preparation of a new release!
refactor(main): Split LOG_NAME & LOG_STREAM variables Splitting these in two lets users better configure how the logs show up in Stackdriver Logging.