Support configuration of custom outputs for fluentd
As an operator, I want to be able to configure the fluentd log collector with a custom output, so that I can aggregate logs using a service other than the elasticsearch instance that may be deployed by kolla-ansible.
Kolla-ansible deploys the fluentd log collector on all hosts in order to collect logs from the containerised services and forward them to a log aggregation service. Support exists for forwarding to an elasticsearch instance deployed by kolla-ansible, but it is not possible to forward logs to an unmanaged elasticsearch instance or other log aggregator such as Splunk or Monasca log API[1].
The proposed change would allow an operator to drop fluentd configuration templates into a directory on the control node, e.g. /etc/kolla/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Mark Goddard
- Direction:
- Needs approval
- Assignee:
- Mark Goddard
- Definition:
- Approved
- Series goal:
- Proposed for pike
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Mark Goddard
- Completed by
- Mark Goddard
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Support configuration of custom fluentd outputs
