Open Joshuaalbert opened 2 years ago
@Joshuaalbert Thanks for the feedback!
Here are some questions to help us better understand your use case
Hi, I'm a bot from the Ray team :)
To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.
If there is no further activity in the 14 days, the issue will be closed!
You can always ask for help on our discussion forum or Ray's public slack channel.
Hi, I'm a bot from the Ray team :)
To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.
If there is no further activity in the 14 days, the issue will be closed!
You can always ask for help on our discussion forum or Ray's public slack channel.
Description
When you have lots of actors and complicated system in production, and you want to respond quickly to an error, it is really hard to open up every single actor log file and then search them from the dashboard. In addition, searching through log files obfuscates the actor name, so it obfuscates clarity.
As a dev ops engineer, I would like:
Use case
When a bug happens in production, and it triggers some alert, we immediately have to find it. Sometimes the bug can be hard to find, as it might be in middleware, frontend, backend, .... However, in all cases we need to inspect the Ray logs. Sometimes it is easy to know where to look, in which actor, but sometimes it's not. And, there's just not enough time to open all the log files.