2024-11-25-ET-W2IT Monday meeting
Date
Nov 25, 2024 13:00-15:00 UTC
 Invited Participants
Jeremy TANDY (ET-W2IT Chair)
Rémy GIRAUD (SC-IMT Chair)
Lei XUE (CMA)
Xinqiang HAN (CMA)
Wenjing GU (CMA)
Hyumin EOM (KMA)
Yoritsugi YUGE (JMA)
Masato FUJIMOTO (JMA)
Steve Olson (NOAA)
Kai Wirt-Thorsten (DWD)
José Mauro(INMET)
Chems eddine ELGARRAI (DGM)
Max Marno (Synoptic)
Kari Sheets (NOAA)
Tom Kralidis (ECCC)
Antje Schremmer (DWD)
WMO Secretariat
Enrico Fucile
Hassan Haddouch
Xiaoxia Chen
David Inglis Berry
Anna Milan
Timo Proescholdt
Meeting agenda
GM overview (20 min) (China/ Morocco)Â
Discussion on Monitoring and Alerting mechanism (40 min)Â
MetricsÂ
dashboardsÂ
Monitor THÂ
Alerts triggeringÂ
Alerts messagesÂ
Incident Management System Â
Jira overview (WMO) (15 min)Â
Discussion on IMS (45 min)Â
When a ticket is to be open Â
Who is eligible to open a ticketÂ
Tickets duplicationÂ
Tickets specification (label, type, …)Â
WorkflowÂ
Meeting Note
GM overview (20 min) (China/ Morocco)Â
Wenjing (CMA) presented the GM (China) dashboard
(Rémy) two roles of Metrics: 1) to identify errors 2) to provide performance (KPI) analysis. To differentiate operational metrics and marketing metrics by grouping is most important.
(Jeremy) process of requesting dashboard? GitHub repo ticket → change the dashboard design
(Rémy) GB, connected flag (e.g BoM has been disconnected for months whereas Zambia was disconnected for serveral days, how can see the difference?)
(Tom) we need to firstly identify the target audiences
Chems shared the GM (Morocco) portal http://wis2live.marocmeteo.ma/ and Grafana dashboard https://wis2gmc.marocmeteo.ma/
Discussion on Monitoring and Alerting mechanism (40 min)Â
MetricsÂ
dashboardsÂ
Monitor THÂ
Alerts triggeringÂ
Alerts messagesÂ
(Tom) updated the GitHub - wmo-im/wis2-monitoring-events: WIS2 Monitoring Events
(Rémy) We need to define the potential scenarios that an event message needs to be published to the monitor TH.
Summary: Both Lei and Chems confirm that they can publish the warning message to Monitor Topic Hierarchy and can create the Jira tickets for error and critical event messages.
(Max) for resolution message (when the errors have been solved): we need to agree on the text of the resolution message.
Incident Management System Â
Jira overview (WMO) (15 min)Â
(Timo) presented the Jira system.
Summary: Automatic tickets can be created only by GM operators. Manual tickets can be created by Global Services, GISCs and Secretariat.
Summary: GISC Watch lead GISC needs to manually check the existing Jira tickets , by checking the source, subject, time and data in the WIS2 event message and then to contact AoR to resolve the tickets,
Â
Next meeting:
9 December
Â