Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
ComputerFrek
@ComputerFrek
oh wait
saw it
sorry
Kókai Péter
@Kokan
np :)
Henrik Grindal Bakken
@hbakken
Hi
@lbudai : I tried to set up a private conversation, but I can do it here if you wish
I added some debug to _release_dynamic_window(), and I get this:
[2019-08-29T14:11:44.933170] Releasing dynamic part of the window; dynamic_window_to_be_released='-100', location='#unknown'
[2019-08-29T14:11:44.933191] Releasing dynamic part of the window; full_window_size='0', location='#unknown'
[2019-08-29T14:11:44.933208] Releasing dynamic part of the window; init+window_size='100', location='#unknown'
Budai Laszlo
@lbudai
@hbakken : hi
Henrik Grindal Bakken
@hbakken
syslog-ng-3.23.1.6.g2069b71.tar.gz <- tried this one
Jacob Bogers
@Jacob_Bogers_twitter
hi
Jacob Bogers
@Jacob_Bogers_twitter
hellloo
Attila Szakacs
@alltilla
@Jacob_Bogers_twitter Hi :)
Gábor Nagy
@gaborznagy
Hi
László Várady
@MrAnno
@gaborznagy Hi, what's up?
ccxcz
@ccxcz
Can I configure message dropping for a slow output? (specifically /dev/tty...)
Fabien Wernli
@faxm0dem
ccxcz: you can play with the queue size
László Várady
@MrAnno
@ccxcz yeah, if you don't use the flags(flow-control) flag in your log path, messages will be dropped after the destination's internal queue is full (you can change this queue size with log-fifo-size()).
However, using this on a file() destination may be tricky, because we have flow-control enabled implicitly.
Jacob Bogers
@Jacob_Bogers_twitter
I am at a loss, I want to replace on of the software components at work (node module uses posix bindings to "openlog", "syslog","setlogmask") with another package at seems to be more low level
we do use syslog-ng as a backend
the protocols are RFC3164, RFC5424, LEEF ,CEF ​​​​​​​
I am trying to find a alternative fo "openlog" without the need of reading all those RFC papers, maybe in the end i need to, but I hope i dont
Peter Czanik
@czanik
this is a test: balabit/syslog-ng moved to syslog-ng/syslog-ng, so I wonder if it still works...
Ah, OK. Activity on the right hand side seems to be up-to-date, so lets hope, that everything else works as well :)
László Várady
@MrAnno
we'll soon ask the Gitter support team to rename this room without removing the chat history (there is no rename option on the UI)
Gábor Nagy
@gaborznagy
Hi @Jacob_Bogers_twitter .
Just my two cents: just took a quick glimpse on the library "SyslogPro", and I don't think you can find a one-one mapping to POSIX APIs, e.g. "openlog" .
They are basically different.
While openlog/syslog is an API to the system logger, SyslogPro library seems like a network-based log forward library.
I guess you need to configure SyslogPro to send the logs to syslog-ng through the network instead of the system logger.
Jacob Bogers
@Jacob_Bogers_twitter
hi
yeah we have syslog-ng listening on 514
(udp)
it seems there is no other way as to learn syslog-ng configuration
or ask the devops to spend time on it to tell us how to use tha pi
thanks Gabor Nagy, can you tell me how long it would take (ballpark estimate) for someone to learn syslog-ng up to a good level?
thank you
Gábor Nagy
@gaborznagy
@Jacob_Bogers_twitter I don't think you need to adjust many things, if syslog-ng on your backend is configured to listen on UDP port 514 (as you stated on cyamato/SyslogPro#3), then you inly need to replace syslog() calls to SyslogPro's send methods, while where you used openlog(), you need to create the connection.
Jacob Bogers
@Jacob_Bogers_twitter
@gaborznagy the WHOLE POINT of my question is HOW you would replace it, there are (counting) 5 different protocols/message formats used, in "syslogpro" js lib , you already stated (quote) "They are basically different."
GUess i am reading the syslog-ng manual and RFC formats,
Stijn Vanorbeek
@StijnVanorbeek_twitter

Hi All, New here to the channel, and also new to syslog-ng.

I'm trying to accomplish the following, but not sure if it is possible:

I successfully have syslog-ng send logs from my embedded devices to a TCP socket, using network()
I see my logs coming in on a socket on the same machine running nc -l -k 8080

Now, I would like to post my logs to an endpoint I'm running in the cloud (using AWS API Gateway).
What would be a good design-pattern. syslog-ng doesn't seem to have a (rest) endpoint type of destination function.

Stijn Vanorbeek
@StijnVanorbeek_twitter
Any suggestions?
Attila Szakacs
@alltilla
Stijn Vanorbeek
@StijnVanorbeek_twitter
@alltilla Thxs! I wasn't yet able to make it work with http(). Ended up using program() to call a Python script to handle the http posts. Do you know if the native http() destination supports batch posting? As I'm working on embedded devices (over the internet) it seems a bit awkward to POST to an end-point for every log line..
Attila Szakacs
@alltilla
Yes, it supports! :) The main options are: body(), body-prefix(), body-suffix(), delimiter() and batch-lines().

The payload will look like:

body-prefix
body
delimiter
body
delimiter
body
body-suffix

where there are batch-lines() number of body

and each body is one log message, formatted as it is set in the config
The output will be one bigger POST request :)
Stijn Vanorbeek
@StijnVanorbeek_twitter
Thxs for pointing this out. I think I was looking at older documentation! The docs are very good, just a lot!
Attila Szakacs
@alltilla
@StijnVanorbeek_twitter You are welcome! :)
Stijn Vanorbeek
@StijnVanorbeek_twitter
@alltilla : I must be missing something. I keep on getting a Plugin module not found in 'module-path'; module-path='/usr/lib/syslog-ng/3.20', module='http' when using http as destination.
I tried to include the module in the config file with @module http