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
{{ message }}
Repository navigation
Commit 572f394
Browse filesBrowse the repository at this point in the historyBrowse files
fix(webapp,clickhouse): treat SQL the caller wrote as their mistake, not ours
The quota list was built on the wrong axis. It classified by resource
limit, but production shows the volume is in plain SQL mistakes: one
error group alone, a missing GROUP BY on the public query API, accounts
for over a million events across hundreds of users, and it stayed at
error level because its code is not a limit.
ClickHouse rejections that mean the SQL itself is wrong now log at warn,
but only when the caller wrote that SQL. The same rejection on TRQL we
generated is our bug and keeps alerting, so the decision is gated on a
userAuthoredQuery flag set by the public query API and the query editor.
Generated dashboard tiles deliberately do not set it.
Drops QUERY_WAS_CANCELLED from the limit list. It was there on the
reasoning that client disconnects would be noisy; it has not fired once
in the last fourteen days, so it was speculation rather than evidence.
0 commit comments