oth
> /var/log/{messages|secure|...} and the journal.
> Ideally, it would be better to have them only in one place.
>
> Thanks,
> Attila
>
> On Tue, Mar 19, 2024 at 4:03 PM Peter Portante via rsyslog
> wrote:
>>
>> Attila, any reason you can't just use persis
Attila, any reason you can't just use persistent journald? That is
what we did to solve the lost shutdown and crash logs. -Peter
On Fri, Mar 15, 2024 at 12:31 PM David Lang via rsyslog
wrote:
>
> imjournal uses the journal api to fetch the logs (fetching them in
> near-real-time), journald keep
On Thu, Jan 4, 2024 at 11:31 AM Rainer Gerhards via rsyslog
wrote:
>
> Hi all,
>
> happy new year to everyone!
>
> I think I have some good news. I have initiated a new project to
> enhance doc and rsyslog website. Initial announcement is here:
>
> https://www.rsyslog.com/improving-the-rsyslog-doc
ry.
>
Agree, did not want to convey that we ignore the return value, but to drop
the sent message that generated the 400 response and move on to try to send
the next message (or batch).
Yes, I'll see what the group wants to do.
Thanks,
-Peter
> David Lang
>
> On Wed, 6 Dec
Hello Rsyslog People!
I have been working with the Ansible team on a use case of rsyslogd
forwarding logs to Splunk via omhttp.
Is there anyway to get movement on a fix for
https://github.com/rsyslog/rsyslog/issues/4348? Would the community be up
for a patch that allowed for a flag to change the
Hi Folks,
I am curious if anybody has a working recipe for collecting logs from a
kubernetes deployment in production, and what pitfalls or gotchas you ran
into. And if you are capturing metadata from Kubernetes pods, containers,
namespaces, etc.
Thanks in advance,
-Peter
__
Great idea, Rainer!
On Mon, Sep 28, 2020 at 12:57 PM Rainer Gerhards via rsyslog <
rsyslog@lists.adiscon.com> wrote:
> Hi folks,
>
> I am doing an experiment tomorrow and invite you to an open (virtual)
> meeting around rsyslog. It's on short notice, and that's part of the
> experiment. More deta
Hi Folks,
I am seeing the following stack trace with a SEGV (filed as BZ
https://bugzilla.redhat.com/show_bug.cgi?id=1549706):
(gdb) where
#0 rsCStrDestruct (ppThis=ppThis@entry=0x7ffed00168f0) at stringbuf.c:216
#1 0x5558a468 in varDestruct (ppThis=0x7ffed86d1bc0) at var.c:72
#2 0x000
8 matches
Mail list logo