You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
What is the outcome that you are trying to reach?
Related to issue #552, add fluent-bit addon and configure logging to cloudwatch and s3.
Describe the solution you would like
Use standard fluent-bit configuration. No special configuration or input for Ray - from Ray clusters, we can use fluentbit sidecar and configuration to move ray logs to stdout, for them to be picked up by the common daemon.
Describe alternatives you have considered
We could also map the ray log path to a hostpath and use additional input of fluentbit to collect the log. Compared to this alternative solution, the proposed sidecar solution gives ray cluster and applications more control and less depended on the EKS cluster configuration.
Additional context
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days
Community Note
What is the outcome that you are trying to reach?
Related to issue #552, add fluent-bit addon and configure logging to cloudwatch and s3.
Describe the solution you would like
Use standard fluent-bit configuration. No special configuration or input for Ray - from Ray clusters, we can use fluentbit sidecar and configuration to move ray logs to stdout, for them to be picked up by the common daemon.
Describe alternatives you have considered
We could also map the ray log path to a hostpath and use additional input of fluentbit to collect the log. Compared to this alternative solution, the proposed sidecar solution gives ray cluster and applications more control and less depended on the EKS cluster configuration.
Additional context
The text was updated successfully, but these errors were encountered: