Skip to content

Commit 4e4aaa2

Browse files
authored
Merge pull request #715 from maykinmedia/chore/update-uwsgi-logs-config
Avoid using `event` key in uwsgi logs
2 parents 0904770 + 6b711c4 commit 4e4aaa2

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

bin/uwsgi.ini

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,9 @@ log-route = uwsgilogger ^((?!\{).)*$
1616

1717
; leave already JSON formatted django logs as is
1818
log-encoder = format:djangologger ${msg}
19-
; Encode uWSGI server logs as JSON
20-
log-encoder = json:uwsgilogger {"source": "uwsgi", "type": "server", "timestamp": "${strftime:%%Y-%%m-%%dT%%H:%%M:%%S%%z}", "event": "${msg}", "level": "info"}
19+
; Encode uWSGI server logs as JSON - deliberately using msg instead of event due to
20+
; high cardinality of this key/label.
21+
log-encoder = json:uwsgilogger {"source": "uwsgi", "type": "server", "timestamp": "${strftime:%%Y-%%m-%%dT%%H:%%M:%%S%%z}", "msg": "${msg}", "level": "info"}
2122

2223
; these are uwsgi's own request logs (not to be confused with the request logs emitted
2324
; by the application!)

0 commit comments

Comments
 (0)