Skip to content

helm, info, status: Check snapshot timestamp for Scan#6205

Open
giner wants to merge 1 commit into
canton-network:mainfrom
giner:stas/helm_info_status_check_snapshot_timestamp_for_scan
Open

helm, info, status: Check snapshot timestamp for Scan#6205
giner wants to merge 1 commit into
canton-network:mainfrom
giner:stas/helm_info_status_check_snapshot_timestamp_for_scan

Conversation

@giner

@giner giner commented Jul 2, 2026

Copy link
Copy Markdown
Contributor
  • Report Scan as lagging if the last snapshot timestamp is older than 4 hours
  • Split reachability and lagging reports (1 means lagging, 2 means unreachable)

- Report Scan as lagging if the last snapshot timestamp is older than 4
  hours
- Split reachability and lagging reports (1 means lagging, 2 means
  unreachable)

Signed-off-by: Stanislav German-Evtushenko <ginermail@gmail.com>
@giner giner force-pushed the stas/helm_info_status_check_snapshot_timestamp_for_scan branch from 22cd809 to aed1452 Compare July 2, 2026 05:50
@giner giner deployed to ci-forks July 2, 2026 05:50 — with GitHub Actions Active

@martinflorian-da martinflorian-da left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks! Not bothering with a cluster test as AFAICT it wouldn't catch any regressions here anyway.

@giner let us know when you're ready to merge

sv: {nodes: $sv, description: "Last status report within \($sv_threshold) seconds"},
mediator: {nodes: $mediator, description: "Last acknowledgment within \($mediator_threshold) seconds"},
scan: {nodes: $scan, description: "Reachable, last open and issuing rounds are within \($scan_threshold) seconds"},
scan: {nodes: $scan, description: "Reachable, last open and issuing rounds are within \($scan_threshold_rounds) seconds and last snapshot is within \($scan_threshold_snapshot) seconds"},

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to explain here that 1 now means lagging and 2 actually unreachable?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The description goes to the UI and having codes explained there may be too verbose and confusing

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could add one more key description_details if you think it's worth it

@martinflorian-da martinflorian-da added the static Used to label PRs for which static tests suffice label Jul 2, 2026
@giner

giner commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

@giner let us know when you're ready to merge

It's ready. Thank you.

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

Labels

static Used to label PRs for which static tests suffice

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants