Seems that uwsgi is masking our log levels, so we get things like:
fork(): Cannot allocate memory [core/master_utils.c line 724]
at INFO level rather than OFAK as it should be.
Seems that uwsgi is masking our log levels, so we get things like:
fork(): Cannot allocate memory [core/master_utils.c line 724]
at INFO level rather than OFAK as it should be.
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T181538 ORES overload incident, 2017-11-28 | |||
Resolved | Ladsgroup | T181546 Let the ORES application set log severity, not uWSGI |
Change 466716 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[operations/puppet@production] ores: Add logstash config
Change 466716 merged by Alexandros Kosiaris:
[operations/puppet@production] ores: Add logstash config
Change 466857 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/services/ores/deploy@master] Start using logstash
Change 466857 merged by Ladsgroup:
[mediawiki/services/ores/deploy@master] Start using logstash
Change 470827 had a related patch set uploaded (by Ladsgroup; owner: Ladsgroup):
[operations/puppet@production] ores: Change logstash port from GELF to json lines
Change 470827 merged by Dzahn:
[operations/puppet@production] ores: Change logstash port from GELF to json lines