Skip to content

fix: name function_logs and event_message in the ClickHouse query_logs hint #376

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.

Sign up for GitHub

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

Open
Rjabov wants to merge 5 commits into
base: main
Choose a base branch
from
Open

fix: name function_logs and event_message in the ClickHouse query_logs hint #376

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6ea0468
fix: name function_logs in the ClickHouse query_logs hint
Rjabov Aug 24, 2026
50051bd
test: assert both Edge Function log sources are named in the ClickHou…
Rjabov Aug 24, 2026
a7a8ef4
fix: point the query_logs hint at event_message for log line text
Rjabov Aug 25, 2026
47bd013
test: assert the ClickHouse hint names event_message
Rjabov Aug 25, 2026
104a789
style: fix indentation on the ClickHouse schemaHint
Rjabov Aug 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions packages/mcp-server-supabase/src/server.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4050,6 +4050,17 @@ describe('feature groups', () => {

expect(queryLogs?.description).toContain('ClickHouse');
expect(sqlDescription).toContain("log_attributes['<key>']");
// Edge Function logs are split across two ClickHouse sources. The hint must
// name both, or the model reaches for `function_edge_logs` (the request
// envelope) when the user asked for console output, which only lives in
// `function_logs`. See getClickHouseLogQuery in logs.ts.
expect(sqlDescription).toContain("'function_edge_logs'");
expect(sqlDescription).toContain("'function_logs'");
// The log line text lives in `event_message`; `log_attributes` carries only
// per-row metadata. Without naming the column the model reads
// `log_attributes`, finds no message key, and reports that the console
// output was never stored. See getClickHouseLogQuery in logs.ts.
expect(sqlDescription).toContain('event_message');
});

test('query_logs advertises the BigQuery dialect when the platform declares it', async () => {
Expand Down
2 changes: 1 addition & 1 deletion packages/mcp-server-supabase/src/tools/debugging-tools.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ const queryLogsByDialect = {
name: 'ClickHouse',
logsNoun: 'unified logs stream',
schemaHint:
"Logs are exposed through a `logs` table; filter by `source` (common values include 'edge_logs', 'postgres_logs', and 'function_edge_logs', but this list is not exhaustive — run `select distinct source from logs` to discover the sources available for this project) and read nested fields via `log_attributes['<key>']`.",
"Logs are exposed through a `logs` table; filter by `source` (common values include 'edge_logs', 'postgres_logs', 'function_edge_logs' for Edge Function invocation/request logs, and 'function_logs' for console output from inside an Edge Function, but this list is not exhaustive — run `select distinct source from logs` to discover the sources available for this project) and read the log line text from `event_message` (the console output or message body); `log_attributes['<key>']` holds only per-row metadata such as level, execution_id and status code.",
}),
bigquery: buildQueryLogsCopy({
name: 'BigQuery',
Expand Down