[MXS-3457] Add logging to stdout in the docker image Created: 2021-03-24 Updated: 2022-09-08 Resolved: 2022-09-08 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Docker |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Trivial |
| Reporter: | Nilnandan Joshi | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 5 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Hi Team, Kindly add logging to stdout in the docker image. Currently, MaxScale being run as a plain process and it being wrapped by a tiny init style wrapper where --log=stdout doesn't added so it will always log to the file. |
| Comments |
| Comment by Nuno Alexandre [ 2021-07-03 ] |
|
We need this to have logging working on our logging infrastructure. I wonder how other customers are redirecting stdout / console output to their fluentbit? |
| Comment by William Scott [ 2022-07-06 ] |
|
@Nuno we've adopted the following workaround, https://jira.mariadb.org/browse/MXS-3995?focusedCommentId=216038&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-216038 However I agree it'd ideally be addressed within the base image. The related ticket also mentions some concerns we have w.r.t. the workaround (e.g. rsyslog was "recently" added, presumably it was introduced for a reason, but we don't have access to the commit history to understand/investigate what that was, etc.). |
| Comment by William Scott [ 2022-09-08 ] |
|
Why was this closed as a won't do? Logging is a fairly important feature. |