<p dir="ltr">Can you pls point me to the direction of the logstash material you mentioned? I would be interested in them whether it'd be possible to port them over.</p>
<div class="gmail_quote">On Apr 20, 2016 7:00 PM, "Scot Needy" <<a href="mailto:scotrn@gmail.com">scotrn@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Some thoughts on my deployment</div><div><br></div><div><b>Logstash</b></div><div>I think I’m going to need to re-introduce logstash just to leverage the existing open source material of logstash filters and Kibana desktops. </div><div>VMware, ASA for example but wanted more real time data. I could probably do the realtime tags with pattendb. </div><div> </div><div><b>syslog-ng counters</b> </div><div>We use an IPAM API to create unique filters, log and destination conf files. The goal was to get unique syslog counters for every VLAN realtime directly from syslog-ng-ctl stats.. </div><div><br></div><div><br></div><div>@include IPAM-filters</div><div><div>filter f_192_168_252_0 { netmask(<a href="http://192.168.252.0/24);" target="_blank">192.168.252.0/24);</a>};</div><div>filter f_192_168_253_0 { netmask(<a href="http://192.168.253.0/24);" target="_blank">192.168.253.0/24);</a>};</div><div>filter f_192_168_254_0 { netmask(<a href="http://192.168.254.0/30);" target="_blank">192.168.254.0/30);</a>};</div></div><div><br></div><div><br></div><div>@include IPAM-dest.conf</div><div><div>destination d_192_168_252_0 { file(/opt/syslog-ng/logs/192_168_252_0/$YEAR$MONTH$DAY-$HOUR-$HOST.log);};</div><div>destination d_192_168_253_0 { file(/opt/syslog-ng/logs/192_168_253_0/$YEAR$MONTH$DAY-$HOUR-$HOST.log);};</div><div>destination d_192_168_254_0 { file(/opt/syslog-ng/logs/192_168_254_0/$YEAR$MONTH$DAY-$HOUR-$HOST.log);};</div></div><div><br></div><div>@include IPAM-log.conf</div><div><div>log { source(s_net); filter(f_192_168_252_0); destination(d_192_168_252_0);};</div><div>log { source(s_net); filter(f_192_168_253_0); destination(d_192_168_253_0);};</div><div>log { source(s_net); filter(f_192_168_254_0); destination(d_192_168_254_0);};</div><div>log { source(s_net); filter(f_192_168_254_4); destination(d_192_168_254_4);};</div></div><div><br></div><div><br></div><br><div><blockquote type="cite"><div>On Apr 20, 2016, at 11:18 AM, Scot Needy <<a href="mailto:scotrn@gmail.com" target="_blank">scotrn@gmail.com</a>> wrote:</div><br><div><br><br>Hi, <br><br> Does anyone have links or care to share notes on making a syslog-ng -> ELK scale for enterprise ? <br><br>I have some ideas and will gladly share my solution but also don’t want to spend days figuring these things out that have already been built. <br>There are many ELK specific references but I also want to make sure the model fits the syslog workload. <br><br><br>Thanks <br><br></div></blockquote></div><br></div><br>______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" rel="noreferrer" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" rel="noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br>
<br></blockquote></div>