_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'
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
file()destination may be tricky, because we have flow-control enabled implicitly.
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.
The payload will look like:
where there are
batch-lines() number of