John Sellens ← Mattermost Feature Proposal Forum My feedback 1 result found add support for syslog output 4 votes Vote Vote Vote Vote We're glad you're herePlease sign in to leave feedback Signed in as (Sign out) Close Close 1 vote 2 votes 3 votes Remove votes You have left! (?) (thinking…) 1 comment · General » Mattermost Team Edition · Delete… · Admin → How important is this to you? Not at all You must login first! Important You must login first! Critical You must login first! We're glad you're herePlease sign in to leave feedback Signed in as (Sign out) Close Close An error occurred while saving the comment John Sellens commented · Aug 2, 2017 · Delete… I like syslog too - but I got the results I wanted without much trouble, so I thought I would share. I run mattermost on centos 7, using systemd, which syslogs by default. In the service definition file I added SyslogIdentifier=mattermost StandardOutput=syslog StandardError=syslog (otherwise it syslog'd as "platform"), and then I turned off file logging in the web interface, so my config.json now has "EnableFile": false, in the "LogSettings" section. Otherwise, I imagine that leaving mattermost logging to "console" and wrapping it with a script that pipes output to logger might do the trick e.g. platform 2>&1 | logger -t mattermost Hope that helps - cheers! John Save Submitting...
I like syslog too - but I got the results I wanted without much trouble, so I thought I would share.
I run mattermost on centos 7, using systemd, which syslogs by default. In the service definition file I added
SyslogIdentifier=mattermost
StandardOutput=syslog
StandardError=syslog
(otherwise it syslog'd as "platform"), and then I turned off file logging in the web interface, so my config.json now has
"EnableFile": false,
in the "LogSettings" section.
Otherwise, I imagine that leaving mattermost logging to "console" and wrapping it with a script that pipes output to logger might do the trick e.g.
platform 2>&1 | logger -t mattermost
Hope that helps - cheers!
John