Open JakeSummers opened 11 months ago
On the dashboard side, we can potentially filter out some of the repeated metadata when fetching the logs. cc: @alanwguo
Before we are able to fix this issue on dashboard side, a workaround will be customizing the formatter of the serve logger and remove the redundant or add metadata you want to? @JakeSummers
RE @scottsun94
Before we are able to fix this issue on dashboard side, a workaround will be customizing the formatter of the serve logger and remove the redundant or add metadata you want to? @JakeSummers
I looked briefly into how to do that, but it wasn't obvious to me. Can you point me in the right direction?
RE @scottsun94
Before we are able to fix this issue on dashboard side, a workaround will be customizing the formatter of the serve logger and remove the redundant or add metadata you want to? @JakeSummers
I looked briefly into how to do that, but it wasn't obvious to me. Can you point me in the right direction?
@sihanwang41 do you have any pointer? Or what's the best way to do it?
hi @JakeSummers , For filtering out ray serve internal logs by requests, ray serve introduce the new logging api (will be out to 2.9). After enable the flag, you are able to disable all the serve internal logs by requests, so that it will be eaiser to check your application log.
Description
When I am developing, I would like to debug my application by easily viewing my application's logs in the ray-dashboard. Right now the application logs are intermixed with the core ray logs.
Full discussion in this slack thread: https://ray-distributed.slack.com/archives/CNCKBBRJL/p1699328167338449
Use case
Currently I log things in ray-serve like this:
As per the instructions here:
This ends up being shown in the ray-serve dashboard like this:
There are several issues with this:
Possible Solution
One solution, to allow me to filter for just my application level logs would be to print the full path of the file:
This would allow my to filter the UI for
my_package
: