Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Monitor Topic #124

Open
antje-s opened this issue Mar 20, 2024 · 2 comments · May be fixed by #144
Open

Monitor Topic #124

antje-s opened this issue Mar 20, 2024 · 2 comments · May be fixed by #144
Assignees
@tomkralidis
Milestone
FT2024-2

Comments

@antje-s
Copy link
Contributor

antje-s commented Mar 20, 2024

In WIS-Guide a monitor topic is mentioned, e.g. under 2.7.3.1 "...Global Broker will not discard the message but will send a message on the monitor topic hierarchy to inform the originating centre and its GISC." and under 2.7.4.1 "...Global Cache decides not to cache data it should behave as though the cache property is set to false and send a message on the monitor topic hierarchy to inform the originating centre and its GISC.". Should we add the monitor value to WTH even if it is a separate subtree, so that everyone is aware of it and for clarity?
tomkralidis added a commit that referenced this issue Jun 3, 2024
@tomkralidis
add clause for monitoring hierarchy (#124)
add82b8
@tomkralidis tomkralidis added this to the FT2024-2 milestone Jun 3, 2024
@tomkralidis tomkralidis self-assigned this Jun 3, 2024
@tomkralidis tomkralidis linked a pull request Jun 3, 2024 that will close this issue
Open
@amilan17
Copy link
Member

amilan17 commented Jun 3, 2024

https://github.com/wmo-im/tt-wismd/wiki/Meeting-2024-06-03 notes:
Tom presented the issue;

@tomkralidis
Copy link
Collaborator

TT-WISMD 2024-06-03:

  • PR at add clause for monitoring hierarchy (#124) #144
  • enumerate a list of issues that each Global Service should report on (perhaps this goes into WNAM)
  • overriding level 5; is there a better way?
  • ACTION: TT-WISMD to review and provide recommendation
  • for reporting, should we use a different version (not a), to clearly indicate a different payload and topic/subtree/logic?

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

@tomkralidis tomkralidis

Labels
None yet
Projects
None yet
Milestone
FT2024-2
Development

Successfully merging a pull request may close this issue.

add clause for monitoring hierarchy (#124) wmo-im/wis2-topic-hierarchy
3 participants
@tomkralidis @amilan17 @antje-s