Skip to content

Merge worker-level alerts into alerts and history endpoints#115

Merged
tekwani merged 1 commit into
tetherto:developfrom
paragmore:feat/merge-worker-level-alerts
Jun 30, 2026
Merged

Merge worker-level alerts into alerts and history endpoints#115
tekwani merged 1 commit into
tetherto:developfrom
paragmore:feat/merge-worker-level-alerts

Conversation

@paragmore

Copy link
Copy Markdown
Contributor

Pool workers (Ocean, F2Pool) build their own alerts and ship them in ext data instead of going through the thing-scoped alert pipeline. This makes the alerts endpoints surface them.

  • getSiteAlerts and getAlertsHistory now also read worker alerts via getWrkExtData and merge them in before summary/dedup/sort
  • Worker alerts arrive in the same flat shape as thing alerts, so no special-casing is needed
  • Workers opt in through ALERT_EXT_DATA_WORKER_TYPES; a down worker is skipped without failing the endpoint

Depends on the pool-worker and ork PRs that produce and aggregate these alerts.

Read worker-level alerts from pool-worker ext data (getWrkExtData 'alerts' /
'alerts-history') and merge them into the site alerts and history-alerts
responses. Worker alerts use the same flat shape as thing alerts, so they need
no special-casing. Workers opt in via ALERT_EXT_DATA_WORKER_TYPES.
@paragmore paragmore force-pushed the feat/merge-worker-level-alerts branch from e785bb5 to 37351fa Compare June 30, 2026 16:51
@tekwani tekwani merged commit a201230 into tetherto:develop Jun 30, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants