Closed
Bug 1142159
Opened 9 years ago
Closed 9 years ago
Send relengapi logs to log-aggregator
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
This should include what's currently going to relengapi.log as well as the Apache access logs.
Assignee | ||
Comment 1•9 years ago
|
||
I set up a SysLogHandler in relengapi.wsgi and deployed that. Data is flowing! Access logs remain TBD
Assignee | ||
Comment 2•9 years ago
|
||
On Amy's advice I reconfigured the SysLogHandler to log to localhost, and also fixed up the formatting so that it produces legit output. I still need to land the puppet patch to make those hosts forward to our aggregators.
Assignee | ||
Comment 3•9 years ago
|
||
# see http://help.papertrailapp.com/kb/configuration/configuring-centralized-logging-from-python-apps/ syslog_formatter = logging.Formatter( '%(asctime)s ' + socket.gethostname() + ' relengapi: %(message)s', datefmt='%b %d %H:%M:%S') sys_log = logging.handlers.SysLogHandler(socktype=socket.SOCK_DGRAM) sys_log.setLevel(logging.INFO) sys_log.setFormatter(syslog_formatter) Apache logs are as simple as http://blog.papertrailapp.com/send-apache-access-logs-to-remote-syslog-in-1-line/
Assignee | ||
Comment 4•9 years ago
|
||
I enabled logging to syslog for all vhosts in the releng cluster, too, in r103928.
Assignee | ||
Comment 5•9 years ago
|
||
OK, looking good! The access logs are pretty voluminous, so we may need to filter those back at some point.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•