Skip to content

API v3alpha: AlertService #5481

Open
Open

Description

@siavashs

Parent: #5450

Deliver one endpoint per PR with only its consumed contracts and dependencies.

Unary order

  • ListAlerts
  • ListAlertGroups
  • PostAlerts

Use internal alert types, current mute state, deterministic filtering/pagination, and reload-safe routing/group reads. Preserve best-effort ingestion; do not claim exact accepted counts without provider support.

ListAlertGroups must support server-side requested grouping for the UI (#5490). Related pagination work: #3297.

Deferred until last

Client-streamed ingestion, WatchAlerts, and WatchAlertGroups. Add each mutation feed with its consumer (#5480). No future RPC stubs.

Activity

  1. added this to the v1.0 milestone on Aug 29, 2026
  2. self-assigned this
    on Aug 29, 2026
  3. siavashs commented on Aug 29, 2026

    @siavashs
    ContributorAuthor

    The generated browser consumer and Alerts UI are tracked in #5490 under parent #5451.

    Before the alert.v3alpha proto freezes, please resolve the existing UI's custom-grouping requirement. Grouping only one paginated ListAlerts page in the browser is incorrect, and fetching all alerts is unbounded. The preferred contract is server-side requested grouping (for example, group_by) on ListAlertGroups; otherwise the UI roadmap requires an explicit maintainer-approved parity exception.

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

Metadata

Metadata

Assignees

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions