Given WCMP2 KPIs will be part of the WIS2 Guide (target is INFCOM-4), coupled with clarifications of how GDCs shall emit metrics on a daily basis, per the below PR (target is FT2026-1):
wmo-im/wis2-guide#211
...this means that GDCs will (likely) run KPI checks on a daily basis and return metrics accordingly.
Some KPI checks involve testing links in a WCMP2 record, specifically:
..which means daily checks on links by GDCs. Note that all other KPIs proposed do not have network/connectivity requirements.
Is this a problem of elevated traffic, especially if a WCMP2 record has numerous HTTP links? Or potentially long running jobs as GDC content grows over time? Options:
- keep as is; daily link checks contribute to better quality metadata with less "link rot"
- make link checking a recommended check that a GDC performs (would need update in the Guide)
- other options?
Thoughts? cc @wmo-im/tt-wismd
Given WCMP2 KPIs will be part of the WIS2 Guide (target is INFCOM-4), coupled with clarifications of how GDCs shall emit metrics on a daily basis, per the below PR (target is FT2026-1):
wmo-im/wis2-guide#211
...this means that GDCs will (likely) run KPI checks on a daily basis and return metrics accordingly.
Some KPI checks involve testing links in a WCMP2 record, specifically:
..which means daily checks on links by GDCs. Note that all other KPIs proposed do not have network/connectivity requirements.
Is this a problem of elevated traffic, especially if a WCMP2 record has numerous HTTP links? Or potentially long running jobs as GDC content grows over time? Options:
Thoughts? cc @wmo-im/tt-wismd