This effort aims to solve three problems: enriching logging information with context to improve filtering, adding possibility to transfer logs over network (Smart Proxy to Foreman server, Capsule to Satellite etc) and enabling integration with 3rd party logging systems (ELK, systemd, rsyslog, syslog-ng) for easier maintenance. This effort will be shipped in Satellite 6.4 and 6.5
List of work items (preliminary): Structured logging in Foreman Rails app with JSON/CEE output (DONE) Ditto but for Foreman Proxy Correlation ID HTTP header support in Foreman Proxy Correlation ID HTTP header support in Candlepin (DONE *) Correlation ID HTTP header support in Pulp (**) Configurable logging pattern and syslog support in Candlepin (DONE *) Configurable logging pattern and syslog support in Pulp (***) Installer changes (optional) Docs on how to set things up with ELK stack Remarks: * - http://www.candlepinproject.org/docs/candlepin/logging.html ** - https://pulp.plan.io/issues/3289 *** - https://pulp.plan.io/issues/3372
Upstream bug assigned to lzap
Hello Re "Docs on how to set things up with ELK stack" lzap made: https://github.com/lzap/foreman-elasticsearch
Thanks for the update, let's keep it opened since Pulp is not yet integrated. It's a bit delayed due to Pulp 3.x work.
Hello lzap Do you know of a ticket that tracks the work in Pulp 3 that is still required for Sat6.6? Would be nice to set that here as a blocker. The issues linked to in Comment 1 are all closed WONTFIX Thank you
(In reply to Stephen Wadeley from comment #5) > Hello lzap > > Do you know of a ticket that tracks the work in Pulp 3 that is still > required for Sat6.6? sorry, 6.8 is target release for Pulp 3
Hello In 6.10 we will have: Bug 1732522 - [RFE] Support for correlation id and syslog in pulp 3
Hello lzap Bug 1732522 - [RFE] Support for correlation id and syslog in pulp 3 is now verified. Can I close this tracker as VERIFIED? Thank you
Thank you and congratulations all! This was a long one.
yes indeed, thank you all