Hi Jan, In the GeoNode project, they make a call to the REST API to check if the GeoNode workspace is available: https://github.com/GeoNode/geonode/blob/3e59b936b3ce938f6b6ba4ccfb9ff3a95c068a78/docker-compose.yml#L90
Alexandre Le ven. 17 déc. 2021 à 08:32, Jan Hoskens via Geoserver-users < geoserver-users@lists.sourceforge.net> a écrit : > So what resource should we use if we are running the Geoserver in a > dockerized environment and need Liveness/Readiness probes to see if > everything is up and running as it should? > > Kind Regards, > Jan > > > > > Op do 16 dec. 2021 om 16:39 schreef Ian Turton <ijtur...@gmail.com>: > >> I'd guess there is something missing from the JSON serializer code that >> skips or doesn't know about those attributes (but to be honest they are >> pretty much hard coded as true in the module lookup code so I wouldn't >> worry about them in general) >> >> Ian >> >> On Thu, 16 Dec 2021 at 15:25, Jan Hoskens via Geoserver-users < >> geoserver-users@lists.sourceforge.net> wrote: >> >>> >>> Hi, >>> >>> When using the REST api as described on >>> https://docs.geoserver.org/latest/en/api/#1.0.0/manifests.yaml , I >>> expect to see a status for each module (isAvailable/isEnabled). But I do >>> not receive the suggested response on the page. >>> >>> I should get: >>> {"about": { >>> "status": [ >>> { >>> "module": "gs-web-core", >>> "name": "GeoServer Web UI Core", >>> "isEnabled": true, >>> "isAvailable": true >>> }, >>> ... >>> >>> I get this instead: >>> >>> { >>> "statuss": { >>> "status": [ >>> { >>> "name": "GeoWeb Cache", >>> "href": >>> "http:\/\/localhost:8080\/geoserver\/rest\/about\/status\/GeoWeb+Cache.json" >>> }, >>> .... >>> >>> I'm trying to find a good endpoint to use as Liveness/Readiness probes >>> for our private Cloud setup, but did not yet find a proper solution. >>> >>> Kind regards, >>> >>> Jan >>> _______________________________________________ >>> Geoserver-users mailing list >>> >>> Please make sure you read the following two resources before posting to >>> this list: >>> - Earning your support instead of buying it, but Ian Turton: >>> http://www.ianturton.com/talks/foss4g.html#/ >>> - The GeoServer user list posting guidelines: >>> http://geoserver.org/comm/userlist-guidelines.html >>> >>> If you want to request a feature or an improvement, also see this: >>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >>> >>> >>> Geoserver-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>> >> >> >> -- >> Ian Turton >> > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Alexandre Gacon
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users