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.

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

Global Caches not caching a significant proportion of data published by GTS-to-WIS2 gateways #1

Open
6a6d74 opened this issue Jan 7, 2025 · 2 comments

Comments

@6a6d74
Copy link

6a6d74 commented Jan 7, 2025

In December @golfvert (Remy) and I noticed that the Global Caches did not seem to be caching much of the data published by GTS-to-WIS2 Gateways. See the image below showing:

  1. number of messages published by "origin" (one of the GTS-to-WIS2 gateways)
  2. number of messages "missed" by the UK-USA Global Cache (i.e., those messages that have not been published by the GC after 10-minutes and are considered to be not cached).
global-cache-performance-gts-data

One issue from DWD's gateway was that the download links in the WNMs weren't resolving, giving the following error:

4XX Not found or no permission

Kai fixed this problem.

Now that WIS2 is operational, we need to determine if this behaviour is still persisting.

(BTW - ignore the Gateway flatlining 3/4 of the way through - that was an offline period)

@6a6d74 6a6d74 changed the title Global Caches not caching a significant proportion of data published by GTS-to-WOS2 gateways Global Caches not caching a significant proportion of data published by GTS-to-WIS2 gateways Jan 7, 2025
@golfvert
Copy link

golfvert commented Jan 7, 2025

I have updated the dashboards for the Sensor Global Cache.
It is accessible at https://grafanab.teganet.eu/dashboards/f/fc0c0ea6-3c87-4e2f-9a0e-27139dc85507/sensor-global-cache
User is wis2pilot.

Drop me an email for the password.
We still have a significant number of messages sent by the gateways not cached. See :

Screenshot 2025-01-07 at 22 04 51

@6a6d74
Copy link
Author

6a6d74 commented Jan 8, 2025

Talking with @golfvert offline, I can confirm that the data excludes recommended data that the Global Caches ignore.

Note that core data with notification messages that state properties.cache=false (i.e., instructing the GC not to cache the data object) should still result in the GC publishing a new notification message - albeit with a URL pointing back to the original source.

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

No branches or pull requests

2 participants