On Mi, 29.09.21 20:21, Arjun D R (drarju...@gmail.com) wrote:
> Hi Lennart,
>
> Please help me understand how the journald is figuring out the PID of the
> log line.
Google SCM_CREDENTIALS.
Lennart
--
Lennart Poettering, Berlin
Hi Lennart,
Please help me understand how the journald is figuring out the PID of the
log line. I believe, with the PID, the journald is able to get the
remaining details (process name) from proc fs. I wonder how the journal is
able to get the PID of the log contributor as there can be many
Hi Lennart,
That's a good idea but still I would like to have the prefix as it is in
the journal . I understand it is impossible to bypass the journal and
expect the direct logging to be the same as journal entries. We can achieve
it through socket but still we cannot have the luxurious prefix as
On Mo, 27.09.21 15:40, Arjun D R (drarju...@gmail.com) wrote:
> Hi Folks,
>
> Currently we are using systemd-journald for service logging. We run
> journalctl for a bunch of services and redirect those to the custom log
> files for every few seconds. This takes up the CPU for that particular
>
Hmm, changes to the service side (for prefix) would be a bit difficult at
the moment. And moreover the journal is a bit luxurious where we get the
timestamp, hostname, process name and it's PID. So I would like to have
that luxury in the logs.
I have a thought raised from your suggestion. Is it
On Tue, Sep 28, 2021, 06:07 Arjun D R wrote:
> Thank you Mantas for the details.
> How do you currently get the logs "every few seconds"?
> > Actually we have a script that will be triggered every 10 seconds. That
> script will run "journalctl -u " and redirect the output to the
> respective log
Thank you Mantas for the details.
How do you currently get the logs "every few seconds"?
> Actually we have a script that will be triggered every 10 seconds. That
script will run "journalctl -u " and redirect the output to the
respective log file. We will run journalctl for around 40-50 services
On Mon, Sep 27, 2021 at 1:11 PM Arjun D R wrote:
> Hi Folks,
>
> Currently we are using systemd-journald for service logging. We run
> journalctl for a bunch of services and redirect those to the custom log
> files for every few seconds. This takes up the CPU for that particular
> time period
Hi Folks,
Currently we are using systemd-journald for service logging. We run
journalctl for a bunch of services and redirect those to the custom log
files for every few seconds. This takes up the CPU for that particular
time period since we have lot of IO operations as well. We came to know
that
