In our geoserver setup a postgres stores is sometimes unavailable. It seems Geoserver doesn't always regain a connection to the db-server. This results in a clean picture which shows the error message. On the other side our monitoring system (zabbix) needs a tcp status error code or the availability of some textual content to confirm the request. Since its a clean picture Geoserver returns an error check is not possible. The WMS parameter for exception format ain't usable because of the restrained conditions of the monitoring system. The monitoring needs a tcp statuscode that the picture couldn't be made. What are the settings on the geoserver to attain this?
-- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Monitoring-Geoserver-tp6109410p7040784.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
