- syslog-ng - lists.balabit.hu

syslog-ng 3.38 UDP errors and missing messages
by Taavi Ansper 11 Feb '25

11 Feb '25

Hi I am running a syslog server that is having problems getting all of the data via UDP. I have gone through most of the tips for making the performance better, but something is still amiss. 1. The syslog-ng server is running in an VM. 8vcpu and 8gb RAM. Debian 12. 2. After restarting or starting the server the UDP errors are tamed. nstat -asz | grep Error UdpInErrors 0 0.0 UdpRcvbufErrors 0 0.0 After 15 minutes or so the errors start to appear. (This amount of errors is after some time.) UdpInErrors 6734175 0.0 UdpRcvbufErrors 6734175 0.0 After some time it starts to receive the packets again. I can see all of this clearly in my graylog graphics that sucks that log data in. (added picture) https://imgur.com/a/eeRpovh It goes like a sinewave up and down every 15 minutes or so. My config looks like this. options { ts-format(iso); frac-digits(6); keep-timestamp(no); chain-hostnames(no); keep-hostname(no); use-dns(yes); use-fqdn(yes); create-dirs(yes); dir-owner(root); dir-group(adm); dir-perm(0750); owner(root); group(adm); perm(0640); log-fifo-size(100000); }; source clients { network( transport(udp) so-rcvbuf(32MiB) log-iw-size(250k) log-fetch-limit(10k) ); network( transport(tcp) max-connections(100) so-rcvbuf(32MiB) log-iw-size(250k) log-fetch-limit(10k) ); }; source forward { network( port(6514) transport(tcp) keep-timestamp(yes) keep-hostname(yes) ); }; destination file { file("/srv/log/${HOST}/${FACILITY}.log"); }; destination forward { network( "192.168.X.X" port(6514) transport(tcp) so-keepalive(yes) disk-buffer( mem-buf-size(512M) disk-buf-size(2048M) reliable(yes) ) ); }; destination graylog { network( "192.168.X.X" port(5140) flags(syslog-protocol) transport(tcp) so-keepalive(yes) disk-buffer( mem-buf-size(512M) disk-buf-size(2048M) reliable(yes) ) ); }; filter graylog { host("^gw-example-") }; log { source(clients); destination(file); destination(forward); flags(flow-control); }; log { source(forward); destination(file); flags(flow-control); }; log { source(clients); filter(graylog); destination(graylog); flags(flow-control); }; My rmem_max is set like so: sysctl net.core.rmem_max net.core.rmem_max = 33445532 Any suggestions? Best regards -- Taavi Ansper taavi.ansper(a)cyber.ee

2 1

The syslog-ng Insider 2025-01: Alpine Linux; Leap 16.0; Alma Linux
by Peter Czanik (pczanik) 16 Jan '25

16 Jan '25

Dear syslog-ng users, This is the 127th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS A syslog-ng container image based on Alpine Linux ------------------------------------------------- Recently, someone suggested I should check out Alpine Linux and prepare a syslog-ng container image based on it. While not supported by the syslog-ng project, an Alpine-based syslog-ng container image already exist as part of the Linuxserver project. https://www.syslog-ng.com/community/b/blog/posts/a-syslog-ng-container-imag… Call for testing: syslog-ng in openSUSE Leap 16.0 ------------------------------------------------- Last week, I submitted syslog-ng to openSUSE Leap 16.0. While the distro is still in a pre-alpha stage, everything already works for me as expected. Well, except for syslog-ng, where I found a number of smaller problems. As such, this blog is a call for testing, both for syslog-ng on openSUSE Leap 16.0 and also for the distribution itself.https://www.syslog-ng.com/community/b/blog/posts/call-for-testing-sy… Experimental syslog-ng container image based on Alma Linux ---------------------------------------------------------- The official syslog-ng container image is based on Debian Stable. However, we’ve been getting requests for an RPM-based image for many years. So, I made an initial version available based on Alma Linux and now I need your feedback about it! https://www.syslog-ng.com/community/b/blog/posts/experimental-syslog-ng-con… WEBINARS * New webinar: “Performance tuning for syslog-ng deployments”. You can register for it at https://www.syslog-ng.com/event/performance-tuning-for-syslog-ng-deployment… * You can learn about upcoming webinars and browse recordings of past webinars at https://www.syslog-ng.com/events/ Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

Creation of manual pages
by Generic Secure-Logging 03 Jan '25

03 Jan '25

syslog-ng features manual pages for the Unix manual system in the doc/ subdirectory. However, these pages are not created when configuring, building and installing syslog-ng with CMake. The autotools config system creates a Makefile with a target manpages when calling configure with the option --enable-manpages. However, the autotools build is broken. The call of make manpages results in the following error ./configure: line 7001: syntax error near unexpected token `newline' ./configure: line 7001: `yes:' make: *** [Makefile:13726: config.status] Error 2 Does anyone know how to create the manual pages in the current version? The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

1 0

Syslog server chaining issue
by Maurya, Shivani 12 Dec '24

12 Dec '24

Hi All, I am using 2 syslog servers on version 3.31. The devices are sending syslog message to 1st syslog server. The 1st syslog server is forwarding the same message to 2nd syslog server. Device --> Syslog Server 1 --> Syslog Server 2 The configurations of 1st syslog server - Options - keep-hostname(yes); use-dns(yes); use-fqdn(yes); Destination - destination d_sec { udp("IP_of_second_syslog" port(514) template("${ISODATE} ${HOST} ${PRIORITY} ${MSG}\n") template-escape(no)); }; The configuration of 2nd syslog server - destination d_syslogFile { file("/var/log/syslog.log" template("${R_ISODATE} ${HOST} ${PRIORITY} ${FACILITY} ${PROGRAM} ${MSG}\n") template-escape(no)); }; Problem - When the syslog message is getting logged at 2nd Syslog server, the ${PRIORITY} of the message is always "notice". And the original severity/priotity of the message is getting captured in the ${PROGRAM} macro. How to capture the priority of the forwarded message on 2nd Syslog server in the ${PRIORITY} macro instead of ${PROGRAM} macro? Regards, Shivani Maurya

3 3

The syslog-ng Insider 2024-12: FreeBSD audit; 4.8.1; conferences
by Peter Czanik (pczanik) 05 Dec '24

05 Dec '24

Dear syslog-ng users, This is the 126th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS FreeBSD audit source for syslog-ng ---------------------------------- Two weeks ago, I was at EuroBSDcon and received a feature request for syslog-ng. The user wanted to collect FreeBSD audit logs together with other logs using syslog-ng. Writing a native driver in C is time consuming. However, creating an integration based on the program() source of syslog-ng is not that difficult. This blog shows you the current state of the FreeBSD audit source, how it works, and its limitations. It is also a request for feedback. https://www.syslog-ng.com/community/b/blog/posts/freebsd-audit-source-for-s… Version 4.8.1 of syslog-ng is now available ------------------------------------------- Version 4.8.1 was released recently. As you could guess from the version number change, it is primarily a bug fix release, but some minor features also slipped in. From this blog, you can learn what changed in syslog-ng 4.8.1 and where you can get its latest stable version. https://www.syslog-ng.com/community/b/blog/posts/version-4-8-1-of-syslog-ng… Where should I present syslog-ng and sudo? ------------------------------------------ Recently I was asked the same question both at my workplace and at EuroBSDCon, the conference where I was presenting: where do you talk next? I had no definite answer. Of course, I am looking forward to the FOSDEM CfP, but I am also looking for new conferences to present syslog-ng and sudo. Do you have any recommendations? https://www.syslog-ng.com/community/b/blog/posts/where-should-i-present-sys… WEBINARS * New webinar: “Performance tuning for syslog-ng deployments”. You can register for it at https://www.syslog-ng.com/event/performance-tuning-for-syslog-ng-deployment… * You can learn about upcoming webinars and browse recordings of past webinars at https://www.syslog-ng.com/events/ Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

The syslog-ng Insider 2024-11: testing; Quickwit; MacPorts
by Peter Czanik (pczanik) 14 Nov '24

14 Nov '24

Dear syslog-ng users, This is the 125th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS A call for syslog-ng testing ---------------------------- After the last syslog-ng release, we started a campaign to close open issues on GitHub. We'd like to continue this effort and call for collaboration from our users and contributors to make OSE even more stable. While unit tests are great (and we do many tests in-house), nothing can replace using syslog-ng in real-world situations. This blog collects some resources about how you can start testing the latest syslog-ng release from GitHub. https://www.syslog-ng.com/community/b/blog/posts/a-call-for-syslog-ng-testi… Working with Quickwit --------------------- We are always looking for new ways to store log messages. Quickwit is a new contender, designed for log storage, and among others, it also provides an Elasticsearch-compatible API. From this blog, you can learn about Quickwit, and how to forward log messages from syslog-ng to it using the Elasticsearch-compatible API. https://www.syslog-ng.com/community/b/blog/posts/first-steps-with-quickwit-… You can also use the OpenTelemetry protocol to send logs to Quickwit with syslog-ng. https://www.syslog-ng.com/community/b/blog/posts/sending-logs-to-quickwit-u… Huge improvements for syslog-ng in MacPorts ------------------------------------------- Recently I wrote about a campaign that we started to resolve issues on GitHub. Some of the fixes are coming from our enthusiastic community. Thanks to this, there is a new syslog-ng-devel port in MacPorts, where you can enable almost all syslog-ng features even for older MacOS versions and PowerPC hardware. Some of the freshly enabled modules include support for Kafka, GeoIP or OpenTelemetry. From this blog entry, you can learn how to install a legacy or an up-to-date syslog-ng version from MacPorts. https://www.syslog-ng.com/community/b/blog/posts/huge-improvements-for-sysl… WEBINARS * New webcast: “Log management superpowers: a PAM Essentials case study”. You can watch it at https://www.syslog-ng.com/webcast-ondemand/log-management-superpowers-a-pam… * You can learn about upcoming webinars and browse recordings of past webinars at https://www.syslog-ng.com/events/ Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

can kv-parser options be from macros
by Evan Rempel 02 Nov '24

02 Nov '24

Does anyone know if I can use the enriching data to set macros that can then be used as kv-parser options. These values might change on a message by message basis. For example: parser p_kv { kv-parser ( prefix("$kv_prefix") value-separator("$kv_vseparator") pair-separator("$kv_pseparator") ); }; -- Evan

2 2

certificate errors result in excessive logging.
by Evan Rempel 21 Oct '24

21 Oct '24

I am using tls configuration with a locally signed certificate. This mans that I have to configure a custom root CA on to all client systems for them to be able to establish the tls connection to my syslog server. When the clients are unable to verify the server certificate, the server logs three messages for every connection attempt syslog-ng[452597]: SSL error while reading stream; tls_error='error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca', location='/etc/syslog-ng/syslog-ng.server.conf:71:17' syslog-ng[452597]: Error reading RFC6587 style framed data; fd='21', error='Connection reset by peer (104)' syslog-ng[452597]: Syslog connection closed; fd='21', client='AF_INET(1.2.3.4:1234)', local='AF_INET(1.2.3.4:1234)' If there are 100's of clients, and they try to reconnect at a fast rate (every 5 seconds) this can result in a large volume of messages. Is there any way to configure the logging rate of these types of errors or get rid of it altogether. Anyone have any comments on this? -- Evan

2 3

Re: [syslog-ng] syslog-ng Digest, Vol 234, Issue 4
by brian hoffman 15 Oct '24

15 Oct '24

Yes, you were spot on. I realized not long after I sent this that the .0 was missing on the end.Thanks!-Brian Date: Tue, 15 Oct 2024 00:32:37 +0000 From: Evan Rempel <erempel(a)uvic.ca> To: "syslog-ng(a)lists.balabit.hu" <syslog-ng(a)lists.balabit.hu> Subject: Re: [syslog-ng] netmask filter issue Message-ID: <YT4P288MB03355F0F965988C4C22978C0B9452(a)YT4P288MB0335.CANP288.PROD.OUTLOOK.COM> Content-Type: text/plain; charset="iso-8859-1" First off, to write a CIDR address correctly you need to use something of the form w.x.y.z/M Your specification is missing the ".z" prtion of the ip address. I think there is also some confusion regarding how netmasks work. The ip address 192.168.128.0 (I assume you want a .0 at the end) written in binary is 11000000.10101000.10000000.00000000 The /17 subnet mask written in binary is 11111111.11111111.10000000.00000000 If we perform a binary AND of these two addresses we get 11000000.10101000.10000000.000000 written in decimal is 192.168.128.0 This means that the FIRST address of this range is 192.168.128.0 If we perform the binary NOT of the subnet mask we get 00000000.00000000.01111111.11111111 When we take the binary OR of this with the IP address (w.x.y.z) we get 11000000.10101000.11111111.1111111 in decimal is 192.168.255.255 which is the last address if the range. The result is that 192.168.1.0/17 means the range 192.168.128.0 -- 192.168.255.255 I hope that helps. -- Evan

1 0

netmask filter issue
by brian hoffman 15 Oct '24

15 Oct '24

I set up a filter to send certain messages matching an IP range to a destination (a simplified version of my actual config).filter f_siem { netmask(192.168.128/17) or}; For some reason this is picking up the address 192.168.63.41, even though it's not in the range. 192.168.63.41 (10101100.00010111.0) does not match the network portion of 192.168.128.0/17 (10101100.00010111.1) but for some reason it's still getting picked up. I know for sure that it is this particular line because when I comment it out the messages are no longer forwarded for that device. Is there something different about the way this netmask directive works in syslog-ng that would cause it to get matched by this filter?-Brian

2 1

The syslog-ng Insider 2024-10: 4.8.0 release; version number; Debian Stable
by Peter Czanik (pczanik) 10 Oct '24

10 Oct '24

Dear syslog-ng users, This is the 124th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS Version 4.8.0 of syslog-ng improves FreeBSD and MacOS support ------------------------------------------------------------- Recently One Identity released version 4.8.0 of its open-source log management application. Learn about some of the new features and bug fixes: why upgrade to the latest syslog-ng version, not only on FreeBSD :-) https://www.syslog-ng.com/community/b/blog/posts/version-4-8-0-of-syslog-ng… Why it is useful to set the version number in the syslog-ng configuration --------------------------------- The syslog-ng configuration starts with a version number declaration. Up until recently, if it was missing, syslog-ng did not start. With syslog-ng 4.8, this is changing. From this blog, you can learn why version information is useful, what workaround you can use if you do not want to edit your syslog-ng configuration on each update, and what changed in version 4.8. https://www.syslog-ng.com/community/b/blog/posts/why-it-is-useful-to-set-th… We are switching syslog-ng containers from Debian Testing to Stable ----------------------------------------------------- For many years, the official syslog-ng container and development containers were based on Debian Testing. We are switching to Debian Stable now. Learn about the history and the reasons for the change now. https://www.syslog-ng.com/community/b/blog/posts/we-are-switching-syslog-ng… WEBINARS * New webcast: “Log management superpowers: a PAM Essentials case study”. You can watch it at https://www.syslog-ng.com/webcast-ondemand/log-management-superpowers-a-pam… * You can learn about upcoming webinars and browse recordings of past webinars at https://www.syslog-ng.com/events/ Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

Syslog-ng needs some karma on Fedora
by Peter Czanik (pczanik) 10 Oct '24

10 Oct '24

Hi, Version 4.8.1 of syslog-ng was released last week. It is a bugfix release, and it contains fixes for problems also reported by members of the Fedora community. The Fedora 41 release is near, so package updates now need some additional testing, and “karma” in Bodhi. You can find information on how to install syslog-ng 4.8.1 from a testing repo on Fedora 41 beta at https://bodhi.fedoraproject.org/updates/FEDORA-2024-4e812b8a23 . This is also the place where you can provide feedback and karma. Thanks for your help! Peter Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

syslog-ng 4.8.1 packages
by Peter Czanik (pczanik) 04 Oct '24

04 Oct '24

Hi, Version 4.8.1 of syslog-ng was released yesterday. Here is the current status of packaging: * As usual, Debian and Ubuntu packages were made available as part of the release process: https://www.syslog-ng.com/community/b/blog/posts/installing-the-latest-sysl… * openSUSE / SLES and Fedora / RHEL unofficial repositories are maintained by me, and now updated to 4.8.1: https://www.syslog-ng.com/community/b/blog/posts/installing-latest-syslog-n… you use the syslog-ng48 repo, then you do not have to change anything, just start an update. * my syslog-ng-stable repos for RPM distros will be updated next week, as I always wait a few days. * updates for FreeBSD ports are now submitted, but might take some time. If you urgently want to test 4.8.1, then you can use ports files from my GitHub repo: https://www.syslog-ng.com/community/b/blog/posts/installing-a-syslog-ng-4-d… Not maintained by us, but as far as I can see, Homebrew and Alpine Linux both already have syslog-ng 4.8.1. Peter Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

fatal error is syslog-ng 4.8 from copr when reading pipe sources.
by Evan Rempel 04 Oct '24

04 Oct '24

I upgraded syslog-ng today from 4.6 to 4.8 and my disk drive almost immediately filled due to the local error from syslog-ng 2024-09-20T11:59:38.760-07:00 hostname syslog.err syslog-ng[600690]: Error invoking seek on file; filename='/var/log/syslog.pipes/mailstats2', error='Illegal seek (29)' This logged repeatedly until the disk filled up. My source definition for that pipe is source mailstats2 { pipe("/var/log/syslog.pipes/mailstats2" log_iw_size(900000) log_fetch_limit(500) flags(no-parse) ); }; Any insight would be useful. -- Evan

2 2

Version 4.8.1 of syslog-ng is now available
by Peter Czanik (pczanik) 03 Oct '24

03 Oct '24

Hi, I'm happy to share that version 4.8.1 of syslog-ng is now available. The focus of this release was bug fixing, but there are a few minor new features also available, like MacPorts support and ElasticSearch datastream support. Please help to spread the word, and share / retweet the release announcement on social media: * https://www.linkedin.com/posts/peterczanik_release-syslog-ng-481-syslog-ngs… * https://fosstodon.org/@PCzanik/113243820863895946 * https://x.com/PCzanik/status/1841838695659274333 For a complete list of changes you can read the release notes: Highlights * elasticsearch-datastream() destinations can be used to feed Elasticsearch data streams<https://www.elastic.co/guide/en/elasticsearch/reference/current/data-stream…>. Example config: elasticsearch-datastream( url("https://elastic-endpoint:9200/my-data-stream/_bulk") user("elastic") password("ba3DI8u5qX61We7EP748V8RZ") ); * (#5069<https://github.com/syslog-ng/syslog-ng/pull/5069>) * building: thanks to Sergey Fedorov and Marius Schamschula, macOS builds now support gcc again. They also updated the MacPort version<https://github.com/macports/macports-ports/blob/30c55ba04d8c0693c18cdf84014…> of syslog-ng (develop). Great work, and thank you so much for your contribution! (#5108<https://github.com/syslog-ng/syslog-ng/pull/5108>) Features * tls(): expose the key fingerprint of the peer in ${.tls.x509_fp} if trusted-keys() is used to retain the actual peer identity in the received messages. (#5068<https://github.com/syslog-ng/syslog-ng/pull/5068>) * syslog-parser: Added the no-piggyback-errors and the piggyback-errors flags to control whether the message retains the original message or not on parse error(s). By default the old behaviour/piggyback-errors flag is active. The following new tags can be added by the syslog-parser to the message when the parsing failed: * no-piggyback-errors: On failure, the original message will be left as it was before parsing, the value of $MSGFORMAT will be set to syslog-error, and a tag will be placed on the message corresponding to the parser's failure. * piggyback-errors: On failure, the old behaviour is used (clearing the entire message then syslog-ng will generate a new message in place of the old one describing the parser's error). * syslog.rfc5424_missing_hostname * syslog.rfc5424_missing_app_name * syslog.rfc5424_missing_procid * syslog.rfc5424_missing_msgid * syslog.rfc5424_missing_sdata * syslog.rfc5424_invalid_sdata * syslog.rfc5424_missing_message (#5063<https://github.com/syslog-ng/syslog-ng/pull/5063>) Bugfixes * syslog-ng-ctl: fix escaping of stats prometheus Metric labels (for example, the ones produced by metrics-probe()) may contain control characters, invalid UTF-8 or \ characters. In those specific rare cases, the escaping of the stats prometheus output was incorrect. (#5046<https://github.com/syslog-ng/syslog-ng/pull/5046>) * wildcard-file(): fix crashes can occure if the same wildcard file is used in multiple sources Because of some persistent name construction and validation bugs the following config crashed syslog-ng (if there were more than one log file is in the /path folder) @version: current @include "scl.conf" source s_files1 { file("/path/*.log" persist-name("p1") ); }; source s_files2 { file("/path/*.log" persist-name("p2") ); }; destination s_stdout { stdout(); }; log { source(s_files1); destination(s_stdout); }; log { source(s_files2); destination(s_stdout); }; * NOTE: * The issue occurred regardless of the presence of the persist-name() option. * It affected not only the simplified example of the legacy wildcard file() but also the new wildcard-file() source. (#5091<https://github.com/syslog-ng/syslog-ng/pull/5091>) * syslog-ng-ctl: fix crash of syslog-ng service in g_hash_table lookup function after syslog-ng-ctl reload (#5087<https://github.com/syslog-ng/syslog-ng/pull/5087>) * file(), stdout(): fix log sources getting stuck Due to an acknowledgment bug in the file() and stdout() destinations, sources routed to those destinations may have gotten stuck as they were flow-controlled incorrectly. This issue occured only in extremely rare cases with regular files, but it occured frequently with /dev/stderr and other slow pseudo-devices. (#5134<https://github.com/syslog-ng/syslog-ng/pull/5134>) * directory-monitor: fixed a main thread assertion crash that might have occurred during syslog-ng stop or restart (#5086<https://github.com/syslog-ng/syslog-ng/pull/5086>) * Config @version: fixed compat-mode inconsistencies when @version was not specified at the top of the configuration file or was not specified at all (#5145<https://github.com/syslog-ng/syslog-ng/pull/5145>) * grpc: Fix potential memoryleak when the grpc module is loaded but not used. (#5062<https://github.com/syslog-ng/syslog-ng/pull/5062>) * s3(): Eliminated indefinite memory usage increase for each reload. The increased memory usage is caused by the botocore library, which caches the session information. We only need the Session object, if role() is set. The increased memory usage still happens with that set, currently we only fixed the unset case. (#5149<https://github.com/syslog-ng/syslog-ng/pull/5149>) * opentelemetry() sources: fix crash when workers() is set to > 1 (#5138<https://github.com/syslog-ng/syslog-ng/pull/5138>) * opentelemetry() sources: fix source hang-up on flow-controlled paths (#5148<https://github.com/syslog-ng/syslog-ng/pull/5148>) * metrics-probe(): fix disappearing metrics from stats prometheus output metrics-probe() metrics became orphaned and disappeared from the syslog-ng-ctl stats prometheus output whenever an ivykis worker stopped (after 10 seconds of inactivity). (#5075<https://github.com/syslog-ng/syslog-ng/pull/5075>) * affile: Fix an invalid lseek call mainly on the pipe() source, but also possible if using affile on pipe like files (pipe, socket and FIFO). (#5058<https://github.com/syslog-ng/syslog-ng/pull/5058>) Other changes * format-json: spaces around = in $(format-json) template function could cause a crash<https://github.com/syslog-ng/syslog-ng/issues/5065>. The fix of the issue also introduced an enhancement, from now on spaces are allowed around the = operator, so the following $(format-json) template function calls are all valid: $(format-json foo =alma) $(format-json foo= alma) $(format-json foo = alma) $(format-json foo=\" alma \") $(format-json foo= \" alma \") $(format-json foo1= alma foo2 =korte foo3 = szilva foo4 = \" meggy \" foo5=\"\") * Please note the usage of the escaped strings like \" meggy \", and the (escaped and) quoted form that used for an empty value \"\", the latter is a breaking change as earlier an expression like key= led to a json key-value pair with an empty value {"key":""} that will not work anymore. (#5080<https://github.com/syslog-ng/syslog-ng/pull/5080>) * building: fixed multiple potentional FreeBSD build errors (#5099<https://github.com/syslog-ng/syslog-ng/pull/5099>) * docker: Changed the container image's base to debian:bookworm. (#5056<https://github.com/syslog-ng/syslog-ng/pull/5056>) Credits syslog-ng is developed as a community project, and as such it relies on volunteers, to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. We would like to thank the following people for their contribution: Andras Mitzki, Attila Szakacs, Balazs Scheidler, Hofi, Kovács Gergő Ferenc, László Várady, Mate Ory, Peter Czanik (CzP), Sergey Fedorov, Marius Schamschula, Szilard Parrag, Tamas Pal, shifter Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

Suppress UTF-8 BOM in incoming network messages
by Jeremy Utley 25 Sep '24

25 Sep '24

I'm trying to use Syslog-NG to receive logs from our anti-virus web console (ESET Protect). I've got the logs coming in successfully, but they seem to be adding a UTF-8 BOM as part of the message: [2024-09-23T19:03:36.709950] Incoming log entry; input='<15>1 2024-09-23T19:03:36.455Z b35f2351-8f78-4414-b964-415939a7b0fb ERAServer 43 - - <feff>{"event_type" : "Audit_Event","ipv4" : "172.17.0.11","ipv6" : "","hostname" : "b35f2351-8f78-4414-b964-415939a7b0fb","source_uuid" : "b35f2351-8f78-4414-b964-415939a7b0fb","os_name" : "","occured" : "23-Sep-2024 19:03:36","group_name" : "","group_description" : "","severity" : "Information","domain" : "Mapped account","action" : "Logout","target" : "35396c68-5017-4ea9-b268-d209f8040de9","detail" : "Logging out mapped account \'Jeremy Utley\'.","user" : "Jeremy Utley","result" : "Success"}', msg='0x7f6020022150', rcptid='0' Because I only care about the JSON data being provided, I'm setting the "flags(no-parse)" option in my network source, and a rewrite filter to remove the initial data as follows: source s_network { network( port(6514) transport("tls") flags(no-parse) tls( key-file("/etc/syslog-ng/certs/syslog.key") cert-file("/etc/syslog-ng/certs/syslog.crt") peer-verify(optional-untrusted) ) ); }; rewrite r_trimjson { subst("^(.*)- - ", "", value("MESSAGE")); }; destination d_json { file("/var/log/json_data.log" template("${MESSAGE}\n")); }; But I can't seem to eliminate the BOM from the output, and that is messing with JSON parsing, since that is added to the beginning of every line (but the first) in my json_data.log file. I tried adding "\xfe\xff" to the rewrite in an attempt to eliminate it, but that didn't work - the rewrite does not even match at that point. Anyone have any suggestions on how I can deal with this? Thanks! Jeremy Utley

2 1

tls problems when chaning the server certificate syslog-ng-4.6.0
by Evan Rempel 13 Sep '24

13 Sep '24

I have a syslog server running syslog-ng-4.6.0 (from the copr repo). I am not seeing any TLS issues in the logs using the existing ca.d certificate and the current server tls certificate. The current tls certificate will expire soon, and the CA used to sign the server certificate can no longer be used. I have created a new server certificate, signed with a new Root CA. This new Root CA has been successfully added to the ca.d folder and is running without error with the current server certificate. When I replace the server certificate with the new one and restart syslog-ng, I start getting a lot of errors in the logs. SSL error while reading stream; tls_error='error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca' The new server certificate validates $openssl verify tls/server.crt tls/server.crt: OK The CA used to sign the certificate is in the ca.d folder with the correct hash. I have to assume that the error is actually revering to the server certificate, but it could be referring to a client certificate. The error goes away when I switch the server certificate back. The only things that changes for this error is using the new server certificate. How do I track this down? Are there any other suggestions on what might have gone wrong? -- Evan

2 2

rewrite in syslog-ng
by Wilson, Jonathan L 12 Sep '24

12 Sep '24

Running OSE version 3.38.1 and having difficulty with a rewrite rule. The logs that I'm trying to modify look like: 2024-09-12T06:39:31-05:00 hostname kernel: [*09/12/2024 11:39:31.9055] bwar: [7649:I:CN_ML] ... What I am trying to do is remove the extra timestamp in square brackets (the first field in square brackets above.) My rewrite rule looks like: rewrite r_bracketed_ts { subst( '^[.+]\s', '', type(pcre), value("MESSAGE")); }; It is invoked from this log statement: log { source(s_BSD_UDP_514); filter(f_something); rewrite(r_bracketed_ts); destination(d_something); flags(final,flow-control); }; The problem is that the rewrite appears to do nothing; log entries come out unmodified. Am I missing something? Thank you - Jon Wilson

2 1

The syslog-ng Insider 2024-09: documentation; TRANSPORT macro; rolling RPMs
by Peter Czanik (pczanik) 11 Sep '24

11 Sep '24

Dear syslog-ng users, This is the 123rd issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS You can also contribute to the syslog-ng OSE documentation ---------------------------------------------------------- The up-to-date syslog-ng Administration Guide received a new look and easier navigation, as well as better search experience. Best of all, you can now also easily contribute to the syslog-ng documentation. https://www.syslog-ng.com/community/b/blog/posts/you-can-also-contribute-to… The $TRANSPORT macro of syslog-ng --------------------------------- Do you want to know how your log messages arrived to syslog-ng? The new $TRANSPORT macro provides you with part of the answer. It shows you the protocol variant for network sources, or the kind of local source used. https://www.syslog-ng.com/community/b/blog/posts/the-transport-macro-of-sys… Rolling RPM platforms added to the syslog-ng package build system ----------------------------------------------------- Syslog-ng uses a container-based system to generate the official source tgz and to build ready-to-use packages for various Linux distributions. Recently, we added support for some rolling RPM Linux distributions, allowing us to spot breaking changes before a stable release of the OS would become available. https://www.syslog-ng.com/community/b/blog/posts/rolling-rpm-platforms-adde… WEBINARS * You can browse recordings of past webinars at https://www.syslog-ng.com/events/ Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

Send GELF log messages to Syslog-NG server
by Roberto Carna 21 Aug '24

21 Aug '24

Hi people, a Graylog server is sending GELF log messages to my Syslog-NG server listening on the UDP/514 port. But when I was reading the message, I noticed it's in binary format. Maybe syslog-ng service converts GELF to binary, because the log is not in syslog format. Is it possible to make Syslog-NG listen on the UDP/12201 port for incoming GELF messages, in addition to UDP/514 syslog port ? Or what can I do to accept GELF messages in the Syslog-NG server and then read them in ASCII format ? Thanks a lot!

3 2

The syslog-ng Insider 2024-08: 4.8.0 release; Prometheus; Amazon Linux
by Peter Czanik (pczanik) 15 Aug '24

15 Aug '24

Dear syslog-ng users, This is the 122nd issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS Version 4.8.0 of syslog-ng improves FreeBSD and MacOS support ------------------------------------------------------------- Recently One Identity released version 4.8.0 of its open-source log management application. Learn about some of the new features and bug fixes: why upgrade to the latest syslog-ng version, not only on FreeBSD :-) https://www.syslog-ng.com/community/b/blog/posts/version-4-8-0-of-syslog-ng… syslog-ng Prometheus exporter ----------------------------- Prometheus is an open-source monitoring system that collects metrics from your hosts and applications, allowing you to visualize and alert on them. The syslog-ng Prometheus exporter allows you to export syslog-ng statistics, so that Prometheus can collect it. While an implementation in Go has been available for years on GitHub (for more information, see this blog entry), that solution uses the old syslog-ng statistics interface. And while that Go-based implementation still works, syslog-ng 4.1 introduced a new interface that provides not just more information than the previous statistics interface, but does so in a Prometheus-friendly format. The information available through the new interface has been growing ever since. The syslog-ng Prometheus exporter is implemented in Python. It also uses the new statistics interface, making new fields automatically available when added. https://www.syslog-ng.com/community/b/blog/posts/syslog-ng-prometheus-expor… Experimental syslog-ng packages for Amazon Linux 2023 ----------------------------------------------------- Last year, I received many requests about syslog-ng for Amazon Linux 2023, but I could not find an easy way to create syslog-ng packages. Recently, however, I found that Fedora Copr supports building packages for Amazon Linux 2023. So, with a little bit of experimentation, I got a cut down version of syslog-ng compiled. https://www.syslog-ng.com/community/b/blog/posts/experimental-syslog-ng-pac… WEBINARS * You can browse recordings of past webinars at https://www.syslog-ng.com/events/ Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

Version 4.8.0 of syslog-ng is now available
by Peter Czanik (pczanik) 24 Jul '24

24 Jul '24

We have new documentation You can find our new up-to-date documentation in the new Administration Guide at syslog-ng.github.io<https://syslog-ng.github.io/admin-guide/README>. Highlights Default config version in configuration files cfg: allow usage of current in config @version by default if it is not presented This change allows syslog-ng to start even if the @version information is not present in the configuration file and treats the version as the latest in that case. NOTE: syslog-ng will still raise a warning if @version is not present. Please use @version: current to confirm the intention of always using the latest version and silence the warning. (#5030<https://github.com/syslog-ng/syslog-ng/pull/5030>) BSD directory monitoring with kqueue directory-monitor: Added a kqueue based directory monitor implementation. wildcard-file() sources are using a directory monitor<https://syslog-ng.github.io/admin-guide/060_Sources/020_File/001_File_follo…> as well to aid detection of changes in the folders of the followed files. The new kqueue-based directory monitor uses far fewer resources than the poll based version on BSD-based systems. (#5022<https://github.com/syslog-ng/syslog-ng/pull/5022>) See more at the new syslog-ng documentation<https://syslog-ng.github.io/admin-guide/060_Sources/020_File/001_File_follo…>. Wildcard file source fine-tuning wildcard-file(): Added a dedicated monitor_freq option to control the poll frequency of the change detection in the directories separately when the poll method is selected via the monitor-method() option. The monitor-method() option controls only the change detection method in the directories, not the following of the file changes, and if poll is the selected method the frequency must not necessarily be the same, e.g. if the (earlier) commonly used follow-freq() is set to 0 for switching to the poll_fd_events method for file content change detection, that also might be meant a directory change poll with zero delays (if monitor-method() was set to poll as well), and that could cause a heavy CPU load unnecessarily. (#4998<https://github.com/syslog-ng/syslog-ng/pull/4998>) See more at the new syslog-ng documentation<https://syslog-ng.github.io/admin-guide/060_Sources/020_File/001_File_follo…>. Features * s3(): Introduced server side encryption related options server-side-encryption() and kms-key() can be used to configure encryption. Currently only server-side-encryption("aws:kms") is supported. The kms-key() should be: To be able to use the aws:kms encryption the AWS Role or User has to have the following permissions on the given key: Check this<https://repost.aws/knowledge-center/s3-large-file-encryption-kms-key> page on why the kms:Decrypt is mandatory. Example config: destination d_s3 { s3( bucket("log-archive-bucket") object-key("logs/syslog") server-side-encryption("aws:kms") kms-key("alias/log-archive") ); }; See the S3<https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.ht…> documentation for more details. (#4993<https://github.com/syslog-ng/syslog-ng/pull/4993>) * an ID of a key * an alias of a key, but in that case you have to add the alias/prefix * an ARN of a key * kms:Decrypt * kms:Encrypt * kms:GenerateDataKey * filter: Added numerical severity settings. The level filter option now accepts numerical values similar to facility. Example config: filter f_severity { level(4) }; This is equivalent to filter f_severity { level("warning") }; For more information, consult the documentation<https://syslog-ng.github.io/admin-guide/080_Log/030_Filters/005_Filter_func…>. (#5016<https://github.com/syslog-ng/syslog-ng/pull/5016>) * opentelemetry(), loki(), bigquery(): Added headers() option Enables adding headers to RPC calls. Example config: opentelemetry( ... headers( "my_header" = "my_value" ) ); (#5012<https://github.com/syslog-ng/syslog-ng/pull/5012>) * Added new proxy options to the syslog() and network() source drivers The transport(proxied-tcp), transport(proxied-tls), and transport(proxied-tls-passthrough) options are now available when configuring syslog() and network() sources. (#4544<https://github.com/syslog-ng/syslog-ng/pull/4544>) Bugfixes * disk-buffer(): fix crash when pipeline initialization fails log_queue_disk_free_method: assertion failed: (!qdisk_started(self->qdisk)) (#4994<https://github.com/syslog-ng/syslog-ng/pull/4994>) * rate-limit(): Fixed a crash which occured on a config parse failure. (#5033<https://github.com/syslog-ng/syslog-ng/pull/5033>) * Fixed potential null pointer deref issues (#5035<https://github.com/syslog-ng/syslog-ng/pull/5035>) * wildcard-file(): fix a crash and detection of file delete/move when using ivykis poll events Two issues were fixed * Fixed a crash in log pipe queue during file deletion and EOF detection (#4989<https://github.com/syslog-ng/syslog-ng/issues/4989>) The crash was caused by a concurrency issue in the EOF and file deletion detection when using a wildcard-file() source. If a file is written after being deleted (e.g. with an application keeping the file open), or if these events happen concurrently, the file state change poller mechanism might schedule another read cycle even though the file has already been marked as fully read and deleted. To prevent this re-scheduling between these two checks, the following changes have been made: Instead of maintaining an internal EOF state in the WildcardFileReader, when a file deletion notification is received, the poller will be signaled to stop after reaching the next EOF. Only after both conditions are set the reader instance will be deleted. * Fixed the file deletion and removal detection when the file-reader uses poll_fd_events to follow file changes, which were mishandled. For example, files that were moved or deleted (such as those rolled by a log-rotator) were read to the end but never read again if they were not touched anymore, therefore switching to the new file never happened. (#4998<https://github.com/syslog-ng/syslog-ng/pull/4998>) * syslog-ng-ctl query: fix showing Prometheus metrics as unnamed values none.value=726685 (#4995<https://github.com/syslog-ng/syslog-ng/pull/4995>) * macros: Fixed a bug which always set certain macros to string type The affected macros are $PROGRAM, $HOST and $MESSAGE. (#5024<https://github.com/syslog-ng/syslog-ng/pull/5024>) * syslog-ng-ctl query: show timestamps and fix g_pattern_spec_match_string assert (#4995<https://github.com/syslog-ng/syslog-ng/pull/4995>) * csv-parser(): fix escape-backslash-with-sequences dialect on ARM csv-parser() produced invalid output on platforms where char is an unsigned type. (#4947<https://github.com/syslog-ng/syslog-ng/pull/4947>) Other changes * bigquery(), loki(), opentelemetry(), cloud-auth(): C++ modules can be compiled with clang Compiling and using these C++ modules are now easier on FreeBSD and macOS. (#4933<https://github.com/syslog-ng/syslog-ng/pull/4933>) * syslog-ng-ctl: do not show orphan metrics for stats prometheus As the stats prometheus command is intended to be used to forward metrics to Prometheus or any other time-series database, displaying orphaned metrics should be avoided in order not to insert new data points when a given metric is no longer alive. In case you are interested in the last known value of orphaned counters, use the stats or query subcommands. (#4921<https://github.com/syslog-ng/syslog-ng/pull/4921>) * s3(): new metric syslogng_output_event_bytes_total (#4958<https://github.com/syslog-ng/syslog-ng/pull/4958>) * multiline-options: Allow multi_line_timeout to be set to a non-integer value. Since multi_line_timeout is suggested to be set as a multiple of follow-freq, and follow-freq can be much smaller than one second, it makes sense to allow this value to be a non-integer as well. (#5002<https://github.com/syslog-ng/syslog-ng/pull/5002>) * packages/dbld: add support for Ubuntu 24.04 (Noble Numbat) (#4925<https://github.com/syslog-ng/syslog-ng/pull/4925>) * packages/dbld: add support for AlmaLinux 9 (#5009<https://github.com/syslog-ng/syslog-ng/pull/5009>) * packages/dbld: added support for Fedora Rawhide and CentOS Stream 9 as testing platforms (#5009<https://github.com/syslog-ng/syslog-ng/pull/5009>) Credits syslog-ng is developed as a community project, and as such it relies on volunteers, to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. We would like to thank the following people for their contribution: Alex Becker, Andras Mitzki, Arpad Kunszt, Attila Szakacs, Balazs Scheidler, Bálint Horváth, Dmitry Levin, Hofi, Ilya Kheifets, joohoonmaeng, ktzsolt, László Várady, Mate Ory, Natanael Copa, Peter Czanik, qsunchiu, Robert Fekete, shifter, Szilárd Parrag, Tamas Pal, Wolfram Joost Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

The syslog-ng Insider 2024-07: logging trends; multiple platforms; sudo; retired platforms
by Peter Czanik (pczanik) 11 Jul '24

11 Jul '24

Dear syslog-ng users, This is the 121st issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS Trends in open source logging ----------------------------- Recently I was asked by Chas Clawson of Sumo Logic what I think about open source log management and telemetry. Needless to say, I also talked about syslog_ng, and in the end I showed a couple of simple syslog-ng configurations sending logs to Sumo Logic. https://www.sumologic.com/blog/securing-open-source-infrastructure-log-all/ Using syslog-ng on multiple platforms ------------------------------------- Your favorite Linux distribution is X. You test everything there. However, your colleagues use distro Y, and another team distro Z. Nightmares start here: the same commands install a different set of syslog-ng features, configuration defaults and use different object names in the default configuration. I ran into these problems while working with Gábor Samu on his HPC logging blog. >From this blog you can learn about some of the main differences in packaging and configuration of syslog-ng in various Linux distributions and FreeBSD, and how to recognize these when configuring syslog-ng on a different platform. https://www.syslog-ng.com/community/b/blog/posts/using-syslog-ng-on-multipl… Working with sudo’s json_compact logs in syslog-ng -------------------------------------------------- Version 1.9.16 of sudo will feature a new option for logging: json_compact. Why is this important? This new format can easily be read and parsed by a log management software, like syslog-ng. Note that in this blog I am showing you a sudo feature which has not yet been released officially. You have to compile sudo yourself. By all means, if you have any other application writing JSON-formatted log messages, you can apply most of what you read here with slight modifications. https://www.syslog-ng.com/community/b/blog/posts/working-with-sudo-s-json_5… syslog-ng OSE 4.7.1 retires some old platforms ---------------------------------------------- Version 4.7.1 of syslog-ng OSE was released recently. It brings many smaller enhancements to metrics, OpenTelemetry and other features, while it also retires support for some older platforms. https://www.syslog-ng.com/community/b/blog/posts/syslog-ng-4-7-1-retires-so… WEBINARS * You can browse recordings of past webinars at https://www.syslog-ng.com/events/ Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0

Help parsing logs
by John Norton 28 Jun '24

28 Jun '24

Hi All, I have a panorama system that sends logs from several devices (dvc_name). What I want to do is have it write to files based on the dvc_name. The dvc_name is in the following message as "ip-10-37-12-142". These are not static as they are spun up as needed and the dvc_name may change. Can you help me figure out how to create a parser or filter to take the following message, where it will read in the dvc_name "ip-10-37-12-142" and write logs that include that dvc_name to a separate file (and other dvc_names it sees in messages to their own file?: *Jun 27 19:08:15 TERL-PANORAMA-01.times.com <http://terl-panorama-01.times.com/> 1,2024/06/27 15:08:14,005655000463255,SYSTEM,dhcp,2817,2024/06/27 15:08:09,,if-renew-trigger,,0,0,general,informational,"DHCP RENEW: interface eth0, ip 10.37.12.142 netmask 255.255.255.224 dhcp server: 10.37.12.129",7383625404611793457,0x8000000000000000,0,0,0,0,,ip-10-37-12-142,0,0,2024-06-27T15:08:09.224-04:00* I've tried a few different things but can't figure out how to do it dynamically. This rewrite worked, but it requires a static entry which won't scale and all potential dvc_names cannot be known: rewrite r_panorama { set("ip-10-37-12-142", value("HOST") condition(message(".*ip-10-37-12-142"))); }; I've also tried creating a filter, but it doesn't actually store what the match finds in a macro that I can replace something like $HOST with. filter f_panorama { match("ip-\d+-\d+-\d+-\d+" value("MESSAGE")); }; I was also thinking that I could do something with the csv parser, but it didn't work like I was expecting, but am thinking a parser might work if I could get it right (I think partially it doesn't work because it is a syslog message and the first part of the message interferes with the csv parsing, not sure): parser p_panorama { csv-parser( columns("future_use1","receive_time","serial_number","log_type","log_subtype","version","generated_time","vsys","event_id","object","future_use3","future_use4","module","severity","description","sequence_number","action_flags","devicegroup_level1","devicegroup_level2","devicegroup_level3","devicegroup_level4","vsys_name","dvc_name") delimiters(",") quote-pairs('""[]') ); }; destination d_panorama {file("`mypath`/panorama/$dvc_name/$dvc_name.log"); }; log { source(s_panother); parser(p_panorama); destination(d_panorama); }; Is this something someone could help me with? Thank you, John

2 1

The syslog-ng Insider 2024-05: documentation; grouping-by(); PAM Essentials; health
by Peter Czanik (pczanik) 09 May '24

09 May '24

Dear syslog-ng users, This is the 120th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news. NEWS The official syslog-ng OSE documentation got a new look ------------------------------------------------------- The syslog-ng Administration Guide received a new look and easier navigation. Not only that, but it is also up-to-date now. Besides, there are now contributor guides available both for the documentation and for syslog-ng developers. The admin guide is available at: https://syslog-ng.github.io/admin-guide/README You can reach all syslog-ng OSE-related documentation at: https://syslog-ng.github.io/ If you find any issues, pull requests and problem reports are welcome. The contributor guide describes how you can fix / extend the documentation. You can report issues at: https://github.com/syslog-ng/syslog-ng.github.io/issues Aggregating messages in syslog-ng using grouping-by() ----------------------------------------------------- Sometimes you have many log messages from an app, but none of them have the exact content you need. This is where the grouping-by() parser of syslog-ng can help. It allows you to aggregate information from multiple log messages into a single message. In this blog, I will show you how to parse sshd logs using the patterndb parser of syslog-ng, and then create an aggregate message from the opening and closing log message using grouping-by. https://www.syslog-ng.com/community/b/blog/posts/aggregating-messages-in-sy… Alerting on One Identity Cloud PAM Essentials logs using syslog-ng -------------------------------------------------- One Identity Cloud PAM Essentials is the latest security product by One Identity. It provides asset management as well as secure and monitored remote access for One Identity Cloud users to hosts on their local network. I had a chance to test PAM Essentials while still in development. While there, I also integrated it with syslog-ng. >From my previous blog, you could learn what PAM Essentials is, and how you can collect its logs using syslog-ng. This blog will show you how to work with the collected log messages and create alerts when somebody connects to a host on your local network using PAM Essentials. https://www.syslog-ng.com/community/b/blog/posts/alerting-on-one-identity-c… The syslog-ng health check -------------------------- Version 4.2 of syslog-ng introduced a healthcheck option to syslog-ng-ctl. It prints three syslog-ng-related metrics on screen – if it can reach syslog-ng, that is. You can use it from scripts to monitor the health of syslog-ng. https://www.syslog-ng.com/community/b/blog/posts/the-syslog-ng-health-check WEBINARS * You can browse recordings of past webinars at https://www.syslog-ng.com/events/ Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://syslog-ng.com/blog/ Peter Czanik (CzP) <peter.czanik(a)oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik

1 0