Use case: Service monitoring setup (Spatineo Monitor)

Janet's goal

Organization X is providing several national level geospatial datasets using OGC WMS and WFS services. The head of the IT unit of the organization X, Janet, is interested in making sure that these services run without problems and that they can allocate the right amoung of computing resources for running them while still keeping the service level on an acceptable level.

Janet's organization has just started using Spatineo Monitor for analyzing the use and the service level of their OGC WxS services, and she want's to make sure that both the services their own organization provides and the background map services used by their map applications, are being monitoried for availability and that their service level stays within the limits communicated to the end-users of those services.

Status information

  • The background maps service are provided by the national mapping agency.
  • The services Janet wants to include in the monitoring have already been discovered by Spatineo using publicly available catalog services.
  • No services have yet been added as monitored for Janet's organization in Spatineo Monitor.

Variation 1: Support for OWS QoS capabilities

  • The software used for providing the WMS and WFS services of X supports providing the QoS information capabilities
  • Janet's team members have added the following QoS declarations in the service capabilities of all the WMS and WFS services of organization X:
    • Yearly minimum service availability percentage: 99% (all services, based on the the INSPIRE requirement)
    • For each service: a representative request and the minimum time for receiving a response for it in the typical situation. The definition of each representative request contains the operation name and a set of limitations defining the boundary conditions for reaching the declared service level.
      • An example: For one of the WMS services a representative request consists of a GetMap operation for layer named "RoadNetwork" with
        • EPSG:4326 as the map projection,
        • image format PNG orJPEG,
        • image size less than or equal to 256 x 256, and
        • style named "NavigatorPlain"
      • The WMS server should be able to return the response map for this kind of operation under 500 milliseconds regardless of the used bounding box.
  • Upon the service discovery, Spatineo Monitor has automatically started to monitor the continuous availability of the services using the representative request information.

Variation 2: No support for the OWS QoS capabilities

  • The software used for providing the WMS and WFS services does not support providing the OWS QoS capabilities information.
  • Upon the service discovery, Spatineo Monitor has automatically started to monitor the continuous availability of the services using the the first layer in the capabilities document and the default image type and 256x256 image size.

Usage scenario

  • Janet logs into Spatineo Monitor and is prompted to find an initial set of the services to add to monitoring.
  • Janet finds the services owned by their organization using search by their domain name, and adds each service as followed.
  • Variation 1:
    • Spatineo Monitor automatically configures the alerting thresholds for this service based in the OWS QoS capabilities information, and provides this information to Janet for confirmation.
    • Janet accepts the suggested alerting thresholds and adds the technical support email of their organization as the alert receiver.
  • Variation 2:
    • Janet verifies and if necessary, corrects the monitoring indicator configuration originally set automatically up by Spatineo Monitor for each of the services: Which layers / feature types to use, which CRSes etc.
    • Janet configures the alerting thresholds by hand for each of the newly monitored indicators for maximum request time.
Topic revision: r1 - 12 Jul 2016, IlkkaRinne
 

This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback