Create logging strategy for containers
Currently we don't aggregate logs at all. If containers die, we lose all logs. Not every containers logs to stdout, so docker logs won't work there. We need to create single strategy to work on logging.
Blueprint information
- Status:
- Complete
- Approver:
- Sam Yaple
- Priority:
- Essential
- Drafter:
- Michał Jastrzębski
- Direction:
- Approved
- Assignee:
- Michał Jastrzębski
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
-
Implemented
- Milestone target:
-
liberty-rc1
- Started by
- Steven Dake
- Completed by
- Sam Yaple
Related branches
Related bugs
Sprints
Whiteboard
At the mid-cycle it was agreed as an initial step we would create a data volume container for logging. This container would allow all logs to aggregate to a single location. Additional blueprints have been created to do more with the logs from there (such as process them in ELKStack), or at the operators discretion, do nothing with the logs and just have them accessible in that central logging container location. -- SamYaple
https:/
Gerrit topic: https:/
Addressed by: https:/
Add log aggregation for Ansible into 'log_data'
Addressed by: https:/
rsyslog container
Addressed by: https:/
Ansible bits to rsyslog
Addressed by: https:/
Templates for rsyslog
Addressed by: https:/
Glance logging to rsyslog
Addressed by: https:/
Nova logging to rsyslog
Addressed by: https:/
Heat logging to rsyslog
Addressed by: https:/
Neutron logging to rsyslog
Addressed by: https:/
Keystone logging to rsyslog
Addressed by: https:/
Cinder logging to rsyslog
Addressed by: https:/
Swift logging to rsyslog
Addressed by: https:/
Murano logging to rsyslog
Addressed by: https:/
Make oslo.log work properly with syslog
Gerrit topic: https:/
Addressed by: https:/
Fix oslo.log
Addressed by: https:/
Make oslo.log work correctly on RDO platforms
Work Items
Dependency tree
* Blueprints in grey have been implemented.
