Add observability to agents server

Open
#4,463 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

Begin by locating the agents server and its hosted/cloud deployment configuration, then review the existing logging, failure handling, and runtime visibility. Define the minimum signals needed to answer whether the server is healthy, capture failures with debugging context, expose resource and load indicators, and document dashboards, queries, and single-node limitations.

Written by the indexing model from the issue text.

Description

Summary

Add baseline observability to the agents server so we can safely run the hosted/cloud deployment for the 0.1 launch.

Context

From the Agents check-in: the main remaining cloud hardening work is observability: error tracking, log collection, metrics, CPU/resource monitoring, and enough visibility to know whether the agents server is healthy or overloaded.

Scope

  • Add error tracking, e.g. Sentry or equivalent, for agents server failures.
  • Add/confirm structured logging and log collection for hosted deployments.
  • Emit useful runtime/service metrics, at minimum:
    • CPU and memory usage
    • request / long-poll load
    • durable-stream serving bottlenecks
    • agent loop failures
    • server/runtime errors
  • Add or document dashboards/queries for basic operational health.
  • Document known single-node limitations and what we should watch after launch.

Acceptance criteria

  • We can answer “is the agents server running and healthy?” from logs/metrics.
  • Exceptions/failures are captured with enough context to debug.
  • Basic resource/load signals are visible for hosted agents server deployments.
Dominant language
TypeScript
Stars
10.4k
Forks
399
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from electric-sql/electric

All issues in electric-sql/electric

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.