On Wed, 11.12.13 14:43, Cecil Westerhof ([email protected]) wrote:
>
> On 12/11/2013 02:25 PM, Cecil Westerhof wrote:
> >>You can to centralized logging with the journal too, by simply making
> >>the journal files you want to look at accessible on the same
> >>machine. This could be done vi
On Wed, 11.12.13 14:25, Cecil Westerhof ([email protected]) wrote:
> >Journald's primary job is local logging, for complex logging setups we
> >recommend installing a logging services like rsyslog.
>
> Would you not loose some of the advantages of journald this way? I
> understand that with
On 12/11/2013 02:52 PM, Reindl Harald wrote:
I just had a little check. Copying is not acceptable. Logging on the log-server
should be real-time
so just install rsyslog and you have the same as before
rsyslog is running here on any machine and journald with Storage=none
I already suggested t
On 12/11/2013 02:25 PM, Cecil Westerhof wrote:
Eventually journald should provide you with both a pull and a push
model, however it currently onyl supports a pull model. Note that for
Where can I information about that, or do you mean copying the files?
You probably mend systemd-journal-gate
Am 11.12.2013 14:43, schrieb Cecil Westerhof:
> On 12/11/2013 02:25 PM, Cecil Westerhof wrote:
>>> You can to centralized logging with the journal too, by simply making
>>> the journal files you want to look at accessible on the same
>>> machine. This could be done via NFS sharing, or by copying th
On 12/11/2013 02:25 PM, Cecil Westerhof wrote:
You can to centralized logging with the journal too, by simply making
the journal files you want to look at accessible on the same
machine. This could be done via NFS sharing, or by copying them to a
central host via rsync or scp or even ftp, whateve
On 12/10/2013 07:16 PM, Lennart Poettering wrote:
As I understand it, journald is mend to log locally. Two methods to
log centrally are, if I have understand it correctly:
- mounting and merging through NFS
- systemd-journal-gateway
Whereby the first would be the preferred method.
That would no
We currently use journal2gelf [1], which we also have a rewrite of
that uses the native Python bindings to the journal. We're probably
dumping our rewrite and adding journal integration to Beaver [2].
[1] https://github.com/systemd/journal2gelf
[2] https://github.com/clifton/beaver
___
On Tue, 10.12.13 12:16, Cecil Westerhof ([email protected]) wrote:
> After giving a presentation about systemd/journald I am seen as the
> expert, so they come to me with the challenges they see.
>
> As I understand it, journald is mend to log locally. Two methods to
> log centrally are, if
Hi Cecil,
- Original Message -
> After giving a presentation about systemd/journald I am seen as the
> expert, so they come to me with the challenges they see.
>
> As I understand it, journald is mend to log locally. Two methods to log
> centrally are, if I have understand it correctly:
>
After giving a presentation about systemd/journald I am seen as the
expert, so they come to me with the challenges they see.
As I understand it, journald is mend to log locally. Two methods to log
centrally are, if I have understand it correctly:
- mounting and merging through NFS
- systemd-jo
11 matches
Mail list logo
