[Watchdog] Imagery "IGN (WMS)": sources/south-america/ar/IGN-vector_wms.geojson broken about editor-layer-index HOT 11 OPEN

This service works fine, but sometimes because of unplanned changes in some layer groups, their cache is truncated leaving GeoServer with the task of reseed tiles under demand. This creates an extraodinary load for the server at intervals going from seconds to few minutes with major lag, so the service isn't wroken but it takes more time than usual to answer the requests.

Is there a way to disable this alert as it is a false positive?
Thanks in advance.

from editor-layer-index.

@Marc-marc-marc

from editor-layer-index.

This service works fine, but sometimes because of unplanned changes in some layer groups, their cache is truncated leaving GeoServer with the task of reseed tiles under demand. This creates an extraodinary load for the server at intervals going from seconds to few minutes with major lag, so the service isn't wroken but it takes more time than usual to answer the requests.

Is there a way to disable this alert as it is a false positive?

Thanks in advance.

![Uploading 299878551...]

from editor-layer-index.

• @rizwan123912

from editor-layer-index.

@Zalitoar

from editor-layer-index.

• - ****

from editor-layer-index.

@Marc-marc-marc

from editor-layer-index.

This service works fine, but sometimes because of unplanned changes in some layer groups, their cache is truncated leaving GeoServer with the task of reseed tiles under demand. This creates an extraodinary load for the server at intervals going from seconds to few minutes with major lag, so the service isn't wroken but it takes more time than usual to answer the requests.

Is there a way to disable this alert as it is a false positive?

Thanks in advance.

from editor-layer-index.

I used to close the issue without actions, may whitelist the imagery id in the check script... @rbuffat what do you think?

from editor-layer-index.

@cicku The script is at the moment broken and currently disabled. So the issue has resolved itself. The script checked if the service did not respond for a few days in a row before creating an issue. It should then close the issue automatically if the server is reachable again. (The script ran once a day). However, due to these false positives, I guess it would be good to rethink if it is a good idea in its current form.

from editor-layer-index.

The script only checks the capabilities doc response time?

from editor-layer-index.