-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFE] Aggregated Logging #697
Comments
Added to #595 as well |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
We should add aggregated logging if one isn't configured on the cluster. I'm not sure if we can do this without having privileged, but perhaps we can ship the logs elsewhere if configured (manageiq-loggers has CloudWatch support, but we can probably support shipping to just about any target).
This would help us with diagnostics, and also might lead to fixing some bugs, such as the automate logs not being available in the UI in podified. Since the worker running automate runs in a different pod than the UI worker, the UI does not have access to the automate logs. Also, there can be multiple workers running the automate role and therefore, logs would be distributed across multiple pods.
Related to ManageIQ/manageiq#19582
@miq-bot add-label enhancement
The text was updated successfully, but these errors were encountered: