Skip to main content

Logs

Kvery records every query execution so you can audit activity and troubleshoot problems. Logs are available both per query and across the whole group.

What is logged​

For each execution Kvery captures details such as when it ran, the HTTP response code it produced, and whether it exceeded the slow-query threshold. This makes it easy to answer questions like "which queries are failing?" or "which queries are slow?"

Group logs vs. query logs​

  • Group log — the combined activity for every query in the group. Start here to get an overview or to find errors across the workspace.
  • Query log — the activity for a single query, useful when you are debugging one specific report or API endpoint.

You can filter logs by response code to quickly isolate, for example, all failed (500) executions or all rejected (403) requests.

Log levels​

The group's log level controls how much detail is recorded. Raise it while debugging and lower it for normal operation to keep logs concise.

Retention​

Logs keep the most recent entries — up to 5,000 per query and 5,000 per group — and older entries roll off automatically. This keeps the log view fast while still covering recent history. See Plans and limits for all operational limits.

Using logs effectively​

  • After publishing an API endpoint, watch the logs to confirm calls succeed and to catch authentication or parameter errors.
  • Sort or filter by the slow-query flag to find optimisation targets.
  • When a scheduled query fails, the log shows the response code and error so you can fix it.