Thanks Francesco, I'll definitely check that resource. Kind regards Jan
Op vr 17 dec. 2021 om 11:59 schreef Francesco Bartoli < francesco.bart...@geobeyond.it>: > Hi, > > I guess GeoHealthCheck (https://geohealthcheck.org/) is what you are > looking for, regardless of being in a containerized environment or not. > Anyway, I don’t think such a product should be something natively supported > by GeoServer. > > Francesco > > Il giorno 17 dic 2021, alle ore 11:49, Alexandre Gacon < > alexandre.ga...@gmail.com> ha scritto: > > To me, since a GeoServer instance could serve dozens of datasource in > different ways, a "standard" status check point should not check all the > external resources but only tell you that it is able to provide services. > > If in your case you need to check that the whole chain is working, I would > implement my own health check making a WMS GetMap or GetFeatureInfo on the > extent served by your datastore. > > Alexandre > > Le ven. 17 déc. 2021 à 11:43, Jan Hoskens via Geoserver-users < > geoserver-users@lists.sourceforge.net> a écrit : > >> When using Geoserver in a containerized environment, there should be some >> way to monitor the application. Simple liveness would be, can I access the >> server throught REST api and get a 200 OK. >> >> But that is not all. GeoServer is using a DB and perhaps more external >> resources, or it might have different modules/workspaces that are needed. >> Therefore it should be able to report that everything is available and the >> complete system is usable. This in order to monitor if the container is up >> and running, but also able to respond to queries. >> >> The status REST api looked a step in that direction, but the response did >> not give any other information than a URL that is even not available when >> used. The documentation is telling another story (out of sync with >> implementation?) and shows more information. Now with the previous comment >> about hard coded json, I get the feeling that GeoServer is not completely >> ready to run in a containerized environment. >> >> Kind regards >> Jan >> >> Op vr 17 dec. 2021 om 11:14 schreef Ian Turton <ijtur...@gmail.com>: >> >>> I'm not sure I'm understanding your problem here, what is wrong with the >>> response you get back? >>> >>> Ian >>> >>> On Fri, 17 Dec 2021 at 07:30, Jan Hoskens <jan.hosk...@aca-it.be> wrote: >>> >>>> 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 >>>>> >>>> >>> >>> -- >>> 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 > > >
_______________________________________________ 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
