BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.staging.osgeo.org//foss4g-2024//talk//H3YPJW
BEGIN:VTIMEZONE
TZID:-03
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1
TZNAME:-03
TZOFFSETFROM:-0300
TZOFFSETTO:-0300
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-foss4g-2024-H3YPJW@talks.staging.osgeo.org
DTSTART;TZID=-03:20241205T121500
DTEND;TZID=-03:20241205T124500
DESCRIPTION:Keeping (OGC) Geospatial Web Services up-and-running is best ac
 commodated by continuous monitoring: not only downtime needs to be guarded
 \, \nbut also whether the services are functioning correctly and do not su
 ffer from performance and/or other Quality of Service (QoS) issues.\nGeoHe
 althCheck (GHC) is an Open Source Python application for monitoring uptime
  and availability of OGC Web Services.\nIn this talk we will explain GHC b
 asics\, how it works\, how you can use and even extend GHC (plugins).\n\nT
 here is an abundance of standard (HTTP) monitoring tools that may guard fo
 r general status and uptime of web services. \nBut OGC web services often 
 have their own error\, "Exception"\, reporting not caught by generic HTTP 
 uptime\ncheckers. For example\, an OGC Web Mapping Service (WMS) may provi
 de an Exception as a valid XML response or\nin a error message written "in
 -image"\, or an error may render a blank image. \nA generic uptime checker
  may assume the service is functioning as from those requests and an HTTP 
 status "200" is returned.\n\nOther OGC services may have specific QoS issu
 es not directly obvious. A successful and valid "OWS GetCapabilities" resp
 onse may not \nguarantee that individual services are functioning correctl
 y. For example an OGC Web Feature Service (WFS) based on a dynamic databas
 e may \nreturn zero Features on a GetFeature response caused by issues in 
 an underlying database. Even standard HTTP checkers supporting "keywords" 
 \nmay not detect all failure cases. Many OGC services will have multiple "
 layers" or feature types\, \nhow to check them all?\n\nWhat is needed is a
  form of semantic checking and reporting specific to OGC services!\n\nGeoH
 ealthCheck (GHC) is an Open Source (MIT) web-based framework through which
  OGC-based web services can be monitored. GHC is written in \nPython (with
  Flask) under the umbrella of the GeoPython GitHub Organization. It is cur
 rently an OSGeo Community Project. \n\nGHC consists of a web-UI through wh
 ich OGC service endpoint URLs and their checks can be managed\, \nand moni
 toring-results can be inspected\, plus a monitoring engine that executes s
 cheduled "health-checks" on OGC service endpoints. \nA database stores res
 ults\, allowing for various forms of reporting.\n\nGHC is extensible: a pl
 ugin-system is available for "Probes" to support an expanding number of \n
 cases for OGC specific requests and -checks. Work is in progress to provid
 e a GHC API for various integrations.\n\nInfo\, sources\, demo: https://ge
 ohealthcheck.org
DTSTAMP:20260516T232644Z
LOCATION:Room II
SUMMARY:GeoHealthCheck - QoS Monitor for Geospatial Web Services - Tom Kral
 idis\, Just van den Broecke
URL:https://talks.staging.osgeo.org/foss4g-2024/talk/H3YPJW/
END:VEVENT
END:VCALENDAR