kolla-ansible/fix-barbican-logging-42068f47fe1e4e4d.yaml at 3b824a0a12ff51fdfaac17893bb1e591307c904d - kolla-ansible - OpenDev: Free Software Needs Free Tools

openstack/kolla-ansible

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

6 lines

153 B

YAML

Raw Blame History

 ---
 fixes:
   - |
     Fixes some configuration issues around Barbican logging. `LP#1891343
     <https://bugs.launchpad.net/kolla-ansible/+bug/1891343>`__