Skip to content

Observer dashboard needs reliable packet metrics and separate traffic freshness #168

Description

@n30nex

The observer UI currently presents observationCount as a packet statistic although the legacy counter advances on general presence calls, including status/neighbour handling. Broker last_packet_at is also advanced by those paths. Period charts use deduplicated stored observations, so the labels describe different counts.

Implement the approved observer release foundation: separate broker presence and packet arrival timestamps; keep the legacy counter compatible and documented; extend observer activity with a common effective window, generated time, selected-period recorded count, last complete hour count, and latest recorded packet timestamp. Counts must reconcile with charts, including unknown payload types, and survive the independent analytics archive. Validate status-only, duplicate broker deliveries, nullable samples, archive expiry and aligned comparison windows with PostgreSQL. Compare CoreScope on matching public key/time bounds without claiming cumulative counter differences are packet loss. Depends on retention PR #167 for the hourly archive foundation.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions