PCzanik,
@PCzanik@fosstodon.org avatar

Why use a http()-based destination in syslog-ng? Because you gain extreme performance and an architecture that is easier to maintain.

https://www.syslog-ng.com/community/b/blog/posts/why-use-a-http--based-destination-in-syslog-ng

Just think of #Splunk, #Elasticsearch / @OpenSearchProject , #SumoLogic & Co.
#LogManagement

apgarcia,
@apgarcia@fosstodon.org avatar

@PCzanik

I have a pretty simple requirement: once a day, slurp the previous day's dhcp syslog output into opensearch. (This is so that operators can respond to subpoena requests; realtime updates are not necessary.) There seems to be a rich selection of programs that can accomplish this, but they all seem rather complex: logstash, vector, fluent, fluent bit, ... Do you know of a simple solution?

PCzanik,
@PCzanik@fosstodon.org avatar

@apgarcia Sending logs once a day is not implemented in syslog-ng, only real-time. Here is a blog describing how to send logs to OpenSearch: https://www.syslog-ng.com/community/b/blog/posts/opensearch-and-syslog-ng All you have to do is to add a filter, most likely something like: program("dhcpd")
Oh, and you might also want to add a disk buffer, so logs are stored temporarily even if OpenSearch is unavailable.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • thenastyranch
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • ethstaker
  • Youngstown
  • mdbf
  • slotface
  • everett
  • rosin
  • ngwrru68w68
  • kavyap
  • khanakhh
  • cubers
  • provamag3
  • tacticalgear
  • osvaldo12
  • GTA5RPClips
  • cisconetworking
  • modclub
  • Durango
  • Leos
  • normalnudes
  • megavids
  • tester
  • anitta
  • JUstTest
  • lostlight
  • All magazines