New `get_logs` tool parameters to reduce context bloat

[sourman]

Feature request

Is your feature request related to a problem? Please describe.

No

I often debug front/backend problems that require viewing EDGE function logs precisely. I have a project with more than 30 EDGE functions. They create a lot of logs. The current get_logs tool dumps the logs for the past 24 hours. This is great but destroys the fine grained context needed to solve problems at hand. Often I trigger a specific issue and I need cursor to just see the logs for he past 5 minutes.

It would be great if get_logs provided additional parameters to help grab the relevant logs from the relevant EDGE function.

Describe the solution you'd like

get_logs fine grained control on time and service logs

A clear and concise description of what you want to happen.

the get_logs tool parameters allow LLMs to select time window and sub service such as a specific EDGE function to grab its logs

Describe alternatives you've considered

Currently I setup a python script that pokes the get_logs tool and then filters the output and provides that as context to cursor so it can focus on the issue

A clear and concise description of any alternative solutions or features you've considered.
One alternative might be to provide a logs option in the Supabase CLI. Currently there is not lgos sub-tool within the CLI, but that would be great as well

Additional context

The get_logs -> Edge functions tool call currently return 40,000 Chars in my project. and the LLM is 100% clueless as to the relevant one because it is so large since there are logs from many unrelated EDGE functions

[sourman]

working on it, but if anyone has recommendations please let me know

My initial plan is to add a filter optional parameter that matches against the event_message and the function name and api path for auth and api. this way if the function name is passed it will get all logs that mention this particular function and all logs of this function itself

[sourman]

I setup a python script that is excellent at grabbing edge function console logs

https://gist.github.com/sourman/600d9479fce97ee7fa5c8a626da37d75

the nice thing about this tool is tat it can accept 2 EDGE function names at a time and interleave the logs so that it is easier to understand the sequence of events

you can see in the screenshot there are two EDGE function names. planner and worker and both show up in the same log