On Mon, 14 Sep 2015, Kaushal Shriyan wrote:
Hi,
I have a specific question related to rsyslog running as client mode. Do i
need to invoke rsyslog client via cron scheduler at a specific time period
specifically during low traffic time period? I am not sure if i keep the
rsyslog daemon set in client mode always running reading the application
logs and then saving it to a local3 facility and then send all data from
the local3 facility to the remote centralized logging rsyslog server which
would result in performance impact on the core applications running on the
same server.
Please find below rsyslog client configs settings.
#/etc/rsyslog.conf
$ModLoad imfile
$InputFileName /data/mysql/error.log
$InputFileTag mysql-error
$InputFileStateFile stat-mysql-error
$InputFileSeverity error
$InputFileFacility local3
$InputRunFileMonitor
local3.* @@hostname:<portnumber>
I will appreciate if there are any recommendations or suggestions as per
the best practices to the above approach.
this configuration doesn't save anything locally, it periodically loooks for
/data/mysql/error.log and anytime it finds something there it sends it to the
remote machine. As long as the remote machine is up, this will be very low
impact (other then the overhead of writing and then reading the data to disk).
If the remote machine is down, rsyslog will remember the meessage and keep
trying to send it, eating some RAM for the messages it's read from disk but not
yet sent.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
