Query logs + health in natural language
The deployment already records what happened; the agent just has to ask well. This capability is a disciplined wrapper over the official Convex MCP's read tools (
logs
,
insights
,
functionSpec
,
status
) that turns operational questions into narrow, evidence-returning queries and hands back answers a human can one-click verify in the dashboard. The discipline is copied from the observability MCP surface that works best in the wild: discover fields before querying, three views not fifteen tools, token-frugal output, and a dashboard deep link on every answer.
Workflow
GUARD: deploy-guard step 0-1 — identify + announce which deployment is being read. Reading logs/insights is read-only; never enable prod mutation flags for an insights pass.
DISCOVER before you query — never guess identifiers. Use
functionSpec
to list the real function names and
status
for the deployment/version. Note the tool limits up front:
logs
takes only
--history
(a COUNT, not a time window),
--success
,
--jsonl
,
--prod
,
--deployment
— there is NO server-side status/function/requestId/time filter;
insights
has no function filter and is cloud dev/prod + user-auth only. So you fetch a recent window and filter CLIENT-SIDE.
PICK ONE OF THREE VIEWS and fetch the raw window, then filter locally:
failures view →
logs --history --jsonl
, then locally keep failures + group by function + error message, returning counts + the first stack per group. Answers 'what's erroring', 'what failed after deploy'.
health view →
insights
(cloud only): the typed 72h read-limit / OCC events. Surface + rank them, but hand perf/cost ROOT-CAUSING and fixes to convex-advisor — emit those as pointer findings, do not own the perf-fix framing here.
trace view →
logs --history --jsonl
then locally filter to one requestId/function to read the full execution. Answers 'why did THIS call fail'.
SCOPE by fetching a bounded recent window (a sensible
--history
count) and filtering client-side to the function/status/requestId asked about; when the window is large, aggregate (counts by function/message) rather than dumping lines.
ANSWER with (a) the one-line finding, (b) the evidence (counts + one representative stack/log line), and (c) WHEN POSSIBLE an agent-constructed dashboard deep link (dashboard.convex.dev, the deployment's Logs/Functions view) for human verification — no tool returns the link, so build it from the deployment name + function; never a raw log dump as the answer.
CROSS-CHECK deploy causality when asked 'did my deploy break this': compare the failure onset (from the log timestamps) against the deployment version from
status
; correlate, don't assert.
HAND OFF, don't fix here: a perf/cost cause → convex-advisor (which owns those fixes); a code defect → convex-reviewer/convex-authz; a live error to react to going forward → monitor/sentinel. Emit findings on the bus (specs/finding.schema.json) — primarily
observability
, with perf/cost as pointer findings to advisor — so a composite pass can pick them up.
Show more
Installs
937
Repository
get-convex/agent-skills
GitHub Stars
42
First Seen
2 days ago
Security Audits
Gen Agent Trust Hub
Pass
Socket
Pass
Snyk
Pass