[systemd-devel] state of journal-upload and journal-remote?

[Florian Klink]

On 20-12-19 13:28:45, Lennart Poettering wrote:
>On So, 22.11.20 11:34, Florian Klink (flokli at flokli.de) wrote:
>
>> Hey,
>>
>> I'm wondering about the current state of journal-upload and journal-remote.
>>
>> Traffic on this list about it has gotten pretty silent, there has been
>> bug reports opened in 2018 about this being somewhat broken:
>>
>> https://github.com/systemd/systemd/issues/9858
>> (and search for other issues).
>>
>> All in all this seems somewhat buggy, underdocumented, and given most
>> people do log forwarding these days by running some other daemons,
>> specific to their environment, which query the journal for logs and
>> forward them on their own, without using any of the
>> journal-upload/journal-remote stuff…
>>
>> Is there anyone actually using this? Would it make sense to deprecate
>> and eventually remove it alltogether?
>
>I think some of the components involved are used, others are not. It
>could certainly use some love to make it round again though.
>
>It's too good to remove I'd say.

The HTTP/openssl bits, too?

> I'd rather see the thing fixed (work
>on that would be minor I guess), and a test added so that it doesn't
>regress again.

We'd certainly need some more docs on the HTTP bits, and wire this into
CI to ensure it keeps working.

As written in 20201122174743.3c4pc64wl5dnf6be at ws.flokli.de, I'd be more
in favour of a `journalctl [--receive]` reading from stdin, and removing
all the networked stuff entirely.

-- 
Florian Klink