Documentation
Find guides, support details, and best practices for using gismon to monitor GIS services.
Getting Started
Add a service from the Services page, let gismon normalize the endpoint URL where needed, and then review service and layer detail pages for status, response times, metadata, and recent checks.
Supported Services
gismon currently supports WFS 2.0.0 and above, ArcGIS Feature Services, as well as ArcGIS Mapservices.
WFS URLs may be added either as base endpoints or as GetCapabilities URLs. ArcGIS service URLs are normalized to the base FeatureServer or MapServer endpoint before they are stored.
Monitoring Behavior
For ArcGIS services, gismon checks the service endpoint and then evaluates each sublayer individually. For WFS services, gismon reads the GetCapabilities document, derives feature types from that response, stores available descriptions, coordinate reference information, and WGS84 bounding boxes, and enriches field metadata by issuing a GetFeature request per feature type.
WFS feature types are shown in the interface like layer records so that existing dashboards and detail views remain usable across service types.
FAQ
Why does a WFS service show feature types instead of traditional layers?
WFS services expose feature types through capabilities documents rather than ArcGIS-style numbered sublayers. gismon maps those feature types into the existing layer-oriented UI.
Why are some WFS fields inferred instead of described explicitly?
Many WFS endpoints do not expose a compact field list in GetCapabilities. To keep the detail page useful, gismon derives field metadata from a single GetFeature response for each feature type.