Hi List,
An idea I came up a while ago but forgot until our services broke today.
How about some health-checking tools built into GeoServer? Currently it’s very hard to administrate from a health perspective because if I get a Null Point Exception(NPE) it could be anything (as a non-dev).
I believe there are a few things that could be automatically checked.
I’m thinking something like the current “Tools” button" (or maybe change “Tools” to “Tools & Health” and have a list of health tools.
Possible health tools (just thinking “aloud” - no idea as to the feasibility):
List all SLD’s in the “styles” directory and indicate ones that are unused (general admin; keeping things tidy).
List all layers - indicate ones that don’t have a working style associated (can cause NPEs).
Any thoughts on this? Any other possible tools? Worth pursuing?
Cheers,
Jonathan
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
We try and put our validation checks into the web administration application (i.e. catch the errors as they are being made). I admit that this does not help those using the REST API
The secret to making your idea us a success is to avoid asking the developers to write these validation checks twice.
Hi List,
An idea I came up a while ago but forgot until our services broke today.
How about some health-checking tools built into GeoServer? Currently it’s very hard to administrate from a health perspective because if I get a Null Point Exception(NPE) it could be anything (as a non-dev).
I believe there are a few things that could be automatically checked.
I’m thinking something like the current “Tools” button" (or maybe change “Tools” to “Tools & Health” and have a list of health tools.
Possible health tools (just thinking “aloud” - no idea as to the feasibility):
List all SLD’s in the “styles” directory and indicate ones that are unused (general admin; keeping things tidy).
List all layers - indicate ones that don’t have a working style associated (can cause NPEs).
Any thoughts on this? Any other possible tools? Worth pursuing?
Cheers,
Jonathan
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
I agree with Jody that validation should be in one place and not duplicated. Ideally, such validation checks would be implemented separate of the web admin UI to support other uses (i.e. some other health check facility) but until then:
One potential tool is to use the gsconfig python library to scan the REST API - this could be used to achieve the unused style check. Combine gsconfig with checking virtual services WMS capabilities (via OWSLib python library for example) for correctness and you can also implement basic health checks for each layer without hitting the global capabilities document.
I’ve used the above approach with good results. Some issues still require digging in to resolve, but at least you get a heads up.
We try and put our validation checks into the web administration application (i.e. catch the errors as they are being made). I admit that this does not help those using the REST API
The secret to making your idea us a success is to avoid asking the developers to write these validation checks twice.
Hi List,
An idea I came up a while ago but forgot until our services broke today.
How about some health-checking tools built into GeoServer? Currently it’s very hard to administrate from a health perspective because if I get a Null Point Exception(NPE) it could be anything (as a non-dev).
I believe there are a few things that could be automatically checked.
I’m thinking something like the current “Tools” button" (or maybe change “Tools” to “Tools & Health” and have a list of health tools.
Possible health tools (just thinking “aloud” - no idea as to the feasibility):
List all SLD’s in the “styles” directory and indicate ones that are unused (general admin; keeping things tidy).
List all layers - indicate ones that don’t have a working style associated (can cause NPEs).
Any thoughts on this? Any other possible tools? Worth pursuing?
Cheers,
Jonathan
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
