[syslog-ng] sending log messages to graylog
Rodney Bizzell
hardworker30 at gmail.com
Tue Nov 6 12:57:42 UTC 2018
If you look to the bottom of the config I have made changes to source(sys)
pointing it to my graylog server. I am reading through the documentation I
am thinking that should send the logs to graylog server I am just asking
I apologize if I am making assumptions. The documentation isn't always
clear, so I am just asking if I want to send /var/logs to my graylog server
do I need to add a new source for var log?
options {
flush_lines (0);
time_reopen (10);
log_fifo_size (250000);
chain_hostnames (off);
use_dns (no);
use_fqdn (no);
create_dirs (no);
keep_hostname (yes);
};
source s_sys {
system();
internal();
udp(ip(0.0.0.0) port(514));
};
source s_net {
udp(ip(0.0.0.0) port(514));
tcp(ip(0.0.0.0) port(514) max-connections(256));
};
destination d_cons { file("/dev/console"); };
destination d_mesg { file("/var/log/messages"); };
destination d_auth { file("/var/log/secure"); };
destination d_mail { file("/var/log/maillog" flush_lines(10)); };
destination d_spol { file("/var/log/spooler"); };
destination d_boot { file("/var/log/boot.log"); };
destination d_cron { file("/var/log/cron"); };
destination d_kern { file("/var/log/kern"); };
destination d_mlal { usertty("*"); };
destination d_graylog {
tcp("graylog.server”
port (12201)
);
};
filter f_kernel { facility(kern); };
filter f_default { level(info..emerg) and
not (facility(mail)
or facility(authpriv)
or facility(cron)); };
filter f_auth { facility(authpriv); };
filter f_mail { facility(mail); };
filter f_emergency { level(emerg); };
filter f_news { facility(uucp) or
(facility(news)
and level(crit..emerg)); };
filter f_boot { facility(local7); };
filter f_cron { facility(cron); };
log { source(s_sys); filter(f_kernel); destination(d_cons); };
log { source(s_sys); filter(f_kernel); destination(d_kern); };
log { source(s_sys); filter(f_default); destination(d_mesg); };
log { source(s_sys); filter(f_auth); destination(d_auth); };
log { source(s_sys); filter(f_mail); destination(d_mail); };
log { source(s_sys); filter(f_emergency); destination(d_mlal); };
log { source(s_sys); filter(f_news); destination(d_spol); };
log { source(s_sys); filter(f_boot); destination(d_boot); };
log { source(s_sys); filter(f_cron); destination(d_cron); };
log { source(s_net); destination(d_graylog); };
log { source(s_sys); filter(f_default); destination(d_graylog);};
log { source(s_sys); filter(f_kernel); destination(d_graylog); };
log { source(s_sys); filter(f_default); destination(d_graylog); };
# Source additional configuration files (.conf extension only)
@include "/etc/syslog-ng/conf.d/*.conf"
89,1 Bot
On Tue, Nov 6, 2018 at 6:22 AM Péter, Kókai <peter.kokai at oneidentity.com>
wrote:
> Hello,
>
> Okay, how did you tried to collect those logs ? (like file, wildcard-file)
>
> --
> Kokan
>
> On Tue, Nov 6, 2018 at 10:17 AM Rodney Bizzell <hardworker30 at gmail.com>
> wrote:
>
>> Logs from var logs
>>
>> On Tue, Nov 6, 2018, 1:03 AM Péter, Kókai <peter.kokai at oneidentity.com
>> wrote:
>>
>>> Hello,
>>>
>>> Please do not assume we know about default configuration, as we do not
>>> know the source of your packages. (of course I could guess, but assumption
>>> are mostly source of errors)
>>>
>>> Yes with **log** you can and should connect source and destination -
>>> just like in your e-mail.
>>>
>>> Could you please be more specific about what you mean by local logs ?
>>> Logs from journal (if you have systemd), logs from files (/var/log/...) ?
>>>
>>> A good bet would be the **system** source, that should detect the system
>>> and choose the appropriate method to collect the host logs.
>>> See:
>>> https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.18/administration-guide/25#TOPIC-1043976
>>>
>>>
>>> I would suggest for you to break up your debugging process:
>>> * Verify if you could send logs to graylog (I think this was done)
>>> * Verify if you could collect local logs (for example print those logs
>>> into a file instead of graylog)
>>>
>>> If the above two are okay, you can connect them with a log and should
>>> work.
>>>
>>>
>>> --
>>> Kokan
>>>
>>> On Mon, Nov 5, 2018 at 9:55 PM Rodney Bizzell <hardworker30 at gmail.com>
>>> wrote:
>>>
>>>> Do I need to do something like this?
>>>>
>>>> # Define TCP syslog destination.
>>>> destination d_net {
>>>> syslog("graylog.example.org" port(514));
>>>> };
>>>> # Tell syslog-ng to send data from source s_src to the newly defined syslog destination.
>>>> log {
>>>> source(s_src); # Defined in the default syslog-ng configuration.
>>>> destination(d_net);
>>>> };
>>>>
>>>> syslog server not sending local logs to graylog
>>>>
>>>>
>>>> On Mon, Nov 5, 2018 at 2:32 PM Péter, Kókai <
>>>> peter.kokai at oneidentity.com> wrote:
>>>>
>>>>> Dear Rodney Bizzell,
>>>>>
>>>>> I would kindly ask you to either start a new thread or reply to with a
>>>>> relevant information in the mailing list. Otherwise it is really hard to
>>>>> send follow up to your and others questions.
>>>>>
>>>>> As to per your question. Probably you want to forward your other logs
>>>>> to where syslog-ng is running :) and configure syslog-ng to receive those
>>>>> other logs, and connect the destination that already can send to graylog
>>>>> with the source that can and does receive other logs.
>>>>>
>>>>> In practice:
>>>>>
>>>>> @version: 3.18
>>>>> @include "scl.conf"
>>>>>
>>>>> source my_s { default-network-driver(); };
>>>>>
>>>>> destination graylog { #graylog destination
>>>>> };
>>>>>
>>>>> log { source(my_s); destination(graylog); };
>>>>>
>>>>> I hope this helps.
>>>>>
>>>>> Best regards,
>>>>> Peter Kokai
>>>>>
>>>>> On Mon, Nov 5, 2018 at 7:52 PM Rodney Bizzell <hardworker30 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> I got syslog to send and echo test message from syslog server to my
>>>>>> graylog box. How do I ensure that my syslog box will send other servers
>>>>>> logs to my graylog box through my syslog server. I am going to setup
>>>>>> ipvsadm as load-balancer to point my legacy application to my syslog server
>>>>>> and then they should get shipped through to graylog. Any information is
>>>>>> greatly appreciated
>>>>>>
>>>>>> ______________________________________________________________________________
>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>>>>> Documentation:
>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>>>>
>>>>>>
>>>>> ______________________________________________________________________________
>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>>>> Documentation:
>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>>>
>>>>>
>>>> ______________________________________________________________________________
>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>>> Documentation:
>>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>>
>>>>
>>> ______________________________________________________________________________
>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>> Documentation:
>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>
>>>
>> ______________________________________________________________________________
>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>> Documentation:
>> http://www.balabit.com/support/documentation/?product=syslog-ng
>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>
>>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20181106/dc532725/attachment-0001.html>
More information about the syslog-ng
mailing list