Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

\uD83D\uDDD3Date

14:30-16:30 UTC

\uD83D\uDC65Participants

ET-W2AT

WMO Secretariat

\uD83E\uDD45Goals

  1. WIS2 Monitoring

\uD83D\uDDE3Discussion topics

Item

Presenter

Notes

1

Rémy

Rémy shared Monitoring Toward an Open Standard Approach

To discuss

  • Metrics: what are they?

  • Tools: what tools to be used

2

Kai

Kai shared WIS Monitoring as a lead of TT-WISMon

  • Two types

    • data monitoring (data availability -]WDQMS)

    • service monitoring

  • Status of TT-WISMon

Question

  • (Jeremy)How many Monitoring Centers are there? and Sensor Centers?

    • (Kai) MC>1; SC at least 1 in one Region.

  • (Enrico) GBON requirement, 4 NWP centers, GDPFS centers, statistics, each MC to know who is serving WMC center, to know where the data is from

  • (Rémy) why is it important to know where the data is from in WIS2.0?

    • (Enrico) In WDQMS, a big GAP in NWP centers to get different data.

  • (Timo) Requirements on functional and non-functional monitoring, then be mapped to metrics for monitoring to avoid ad-hoc solutions.

    • (Jeremy) Technology and tools can help monitor everything. But we only need to monitor important metrics.

  • (Kenji) Who to monitor it? How often shold be checking the dashboard?

    • (Enrico) Regional WIGOS to react to the incidents. People will take care when there is a big lack of data.

    • (Jeremy) the monitoring is to identify the issues.

    • (Hassan) Messages to be sent to the poor performance centers.

  • (Rémy) Requirement for WDMQS be described in data model by open statndard. A neutral assessment or a third party to monitor the FTP/SFTP/HTTPS services is enough. But not all NC/DCPC to run the tool for the metrics.

  • (Hassan) Monitoring is to follow up the issues and the producet improvement. WIS2 monitroing is to build a link between the global monitoring and the data/information producers.

(Rémy) applicability of the data model from open standard metrics

(Jeremy) how long does it take to take for the requirements?

Action: Kai & Timo: Initial assessment for the functional and non functional requirements ready in 3-4 weeks

  • (Kenji) Is product also in the scope of WIS2 monitoring?

    • (Jeremy) Within WIS2, data sharing, foundation level, are we defining a mechanism . There could be WIS2 Product monitoring with programmes.

    • (Enrico) There was a GAP between WIS and other activity, such as GDPFS products --to be in WIS catalogue.

  • Vote: Should we define a standard for the metrics document?

    • Ken and Peter: not clear

    • Jeremy, Rémy, Kai, Thorsten, Enrico, Hassan: agrees

  • (Jeremy) Do we introduce the “Sensor Center” in WIS2 Architecture?

    • (Kai) Each node will be a sensor center; data monitoring: only need to assign the role of sensor centers

    • (Rémy) generic sensor center component,

    • (Hassan) how do we deal with the duplication of the data receiver

✅Action items

  • Kai (together with Timo) to prepare the requirements assessment for WIS2 monitoring (functional and non-functional metrics)

⤴Decision

  • A global monitoring dashboard for a real-time view

  • No labels