Skip to content

API monitoring: every API, full analysis, dashboards and service health (M16) #63

Closed as not planned

Description

@productdevbook

API monitoring for the workspace's own APIs: any project, written in any framework, sends its request records, health and uptime to Yuva through a middleware or OpenTelemetry, and the workspace gets request volume, errors and latency per route, consumers, alerts and uptime, custom dashboards like Grafana, the health of every service and its dependencies, and public status pages on the workspace's own domain. Separate from visitor analytics (#42, M15), which counts visits and cannot compute percentiles from event props.

Steps (each its own issue, each shippable):

Web SDK server helpers this builds on: #60, #61, #62.

Decided in docs/architecture.md › API monitoring (M16): an API is an analytics property of kind api;
no row per request is stored (minute, hour and day rollups with mergeable sketches); sampling is off by
default and, when an SDK samples, shows as "estimated".

Done when

See docs/roadmap.md › M16 Accept.

Activity

  1. changed the title [-]API monitoring: request volume, errors and latency per route[/-] [+]API monitoring: every API, full analysis, dashboards and service health (M16)[/+] on Oct 14, 2026
  2. productdevbook commented on Oct 14, 2026

    @productdevbook
    OwnerAuthor

    Closed for now: the API monitoring work moved off main into #72 and is not on the roadmap until that PR is reviewed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions