b649ae922f
Fluentd config actually used two keywords to named log level: "log_level" and "severity_label". This doesn't allow to search and sort ALL logs in Kibana using a unique field (ex: log_level). This fix standardize log level keyword naming. Closes-Bug: #1713410 Change-Id: Ibb2eaf3b6aa21ce6f7945e768e6362c0d40f0507
11 lines
489 B
Django/Jinja
11 lines
489 B
Django/Jinja
<filter openstack_python>
|
|
@type parser
|
|
reserve_data true
|
|
format grok
|
|
key_name message
|
|
grok_pattern %{TIMESTAMP_ISO8601:Timestamp} %{NUMBER:Pid} %{LOGLEVEL:log_level} %{NOTSPACE:python_module} \[(?:req-(?:%{NOTSPACE:request_id}) (?:%{NOTSPACE:user_id}) (?:%{NOTSPACE:tenant_id}) (?:%{NOTSPACE:domain_id}) (?:%{NOTSPACE:user_domain}) (?:%{NOTSPACE:project_domain})|-)\] %{GREEDYDATA:Payload}
|
|
time_format "%Y-%m-%d %H:%M:%S.%L"
|
|
time_key Timestamp
|
|
keep_time_key true
|
|
</filter>
|