Doug Szumski 1ff4e58d70 Fix Barbican API log config ... There are a few issues fixed here: - The Barbican API service doesn't set a log file, so all the Barbican API service logs go to loadwsgi.py.log by default. - The logs in loadwsgi.py.log are not ingested properly by Fluentd. - uWSGI logs go to barbican-api.log. This would normally be used as the log file for the Barbican API service logs. This patch makes the following changes to address the above issues: - All uWSGI logs (from the Emperor and Vassals) go to barbican_api_uwsgi_access.log Although these logs aren't strictly all access logs, this follows the existing pattern for WSGI logs. - The Barbican API service logs are written to barbican-api.log instead of loadwsgi.py.log. This follows the pattern used by other OpenStack services. - Fluentd is configured to parse the Barbican API service logs as it would with other OpenStack Python services. Change-Id: I6d03fa8c81c52b6f061514a836bbd15bb6639aaf Closes-Bug: #1891343		2021-01-27 17:24:58 +00:00
..
defaults	Remove retired Searchlight support	2020-12-15 18:37:34 -06:00
handlers	Simplify handler conditionals	2019-06-27 15:57:19 +00:00
tasks	Merge "Revert "Performance: Use import_tasks in the main plays""	2020-12-15 19:52:24 +00:00
templates	Fix Barbican API log config	2021-01-27 17:24:58 +00:00