Spatineo Monitor FAQ

Find out an answer to your query from Frequently Asked Questions. You can also visit the contact page to send us a message or to call us.

What is Spatineo Monitor?

Spatineo Monitor is a web-based service to monitor and analyse your spatial web services in order to improve the quality of service. With Spatineo Monitor you can analyse the service quality, identify bottlenecks, get alerts when you should react to someone situation, know exactly who is using your spatial web services and how, run OGC and INSPIRE validation on your services, see annual uptimes, get overviews and reports, communicate with your user community and adjust just how your services are monitored. All in in Spatineo Monitor is all you need to ensure that you’re INSPIRE compliant and to improve your quality of service.
 

How does Spatineo Monitor work?

Monitoring data for Spatineo Monitor is collected continuously around the clock by a set of servers forming the Spatineo Monitoring Agent Network. Each of the monitored Spatial Web Services is sent a lightweight test request every 5 minutes. The results of these requests are analysed for possible errors, and the results are recorded in our monitoring database with other statistics such as the server response time.

The monitoring network simulates real-world usage of the services by slightly varying the request parameters, such as the bounding box, to eliminate unrealistic response times created by caching the responses at the server side or by proxies between the server and the Monitoring Agents. The request generation uses intelligent self-learning algorithms to automatically focus to areas with a reasonable amount of provided visual information.

The monitoring data from the Monitoring Agents is delivered to the Spatineo Monitor application as well as the alerting system in near real-time: The results will be visible in the Spatineo Monitor within seconds from receiving the responses of monitoring requests.

The Monitoring Agent Network is running in a highly scalable and reliable Amazon AWS Cloud Computing platform. The Monitoring Agent Network currently processes about 3,5 million requests each day to keep track of over 12000 monitored services around the world. By using the European AWS data centres we can ensure that all the monitoring network traffic as well as stored data from our European customers stays within Europe.
 

How does the monitoring from Spatineo affect the performance of my services?

We’ve done everything to minimize any effects of our monitoring. We send a lightweight GetMap request every 5 minutes to your service. That’s 12 requests per hour. It shouldn’t have any effect whatsoever on your services.
 

What if I don’t want that Spatineo monitors my public spatial web services?

If you’re considering blocking the monitoring from Spatineo, we urge you to consider if the monitoring is really taking anything away from you? Or do your users appreciate having availability statistics publicly available? And would you in general like to have your services to be found by as many potential users as possible?

If you’re your mind is still made up and you wish to cease monitoring your services please refer to our robots.txt guidelines as how to setup an exclusion of robots for your services.
 

Do I need to install something to use Spatineo Monitor?

No, you don’t need any installations and you can get started with Spatineo Monitor in just few minutes. We’re collecting all the data for our monitoring and analysis by automatically accessing your services through the public, standard interfaces (such as WMS, WMTS, WFS).
 

How real time is Spatineo Monitor really?

The results of every single monitoring request are analysed within seconds and they are then immediately visible in Spatineo Monitor.
 

Which spatial web services do you support and is it limited to certain technologies or spatial servers?

We currently support WMS 1.1.1., WMS 1.3.0, WMTS 1.0.0, WFS 1.0.0, WFS 1.1.0, WFS 2.0.0 and ArcGIS MapServer 9.3+. There are no limitations as to what technologies you are running to provide your spatial web services as long as they comply with the standards mentioned here.
 

If there are no installations how do you get the usage analytics data?

For the usage analytics we require the access log from your frontend web server. Please see our Monitor Log Upload Guide on how you can easily set up your system to send the log files automatically to us. The log files are transferred using secure FTP (SFTP) so there’s no risk to your data security.
 

What about data security and confidentially? What do you do with my data?

Your own data (server logs) that you transfer to us are all handled confidentially and they are never given to any third party. In fact in most cases we delete the log after the analysis has been made and we only store the aggregated date you can see in Spatineo Monitor. Please note that for this reason you are responsible for maintaining backup of your server logs should they be needed in future – for instance for a re-analysis to take advantage of some new analysis features that we’ve developed after the point when that particular log was created and analysed.
 

You are using Amazon cloud services to provide Spatineo Monitor. Do I need to worry that my data would leave the protection of my local legislation or that it could come subject to American intelligence activities or such?

No. All the data for our European customers are at all times kept within Europe and it never leaves Europe.
 

How do I sign up?

Please fill in our Registration Form and we will setup an account for you. We’re offering the first two weeks free of charge as a trial period without any strings attached. Please note that to sign up you need to tell us what are your own spatial web services that you would like to monitor in Spatineo Monitor (URL for GetCapabilities). If you want to take advantage of the usage analytics you will also need to send us the server logs (access log from your frontend web server). You can either automate this or for the trial just send us an extract (one week for instance) of your log files. All log files are handled confidentially and are deleted after your trial if you don’t wish to subscribe to the service.

To order the service after the trial period please fill in the Order Form and return it to us duly signed. The Appendices to the Service Order you can find on the Terms of Service document.
 

What does it cost and what is the agreement term?

The first month is a cost-free trial. Thereafter we offer different subscriptions based on your organisation and size. Please refer to our pricing for more information. You only pay as long as you are satisfied with the service, receive value and want to continue using the service. That said, for practical reasons the agreement term is a calendar year and we send one annual invoice for the service to keep the administrative work for you and for us to minimum.
 

I would like to know which requests are coming from Spatineo. What are the IP addresses for your test servers?

Our monitoring requests come from various changing IP addresses in Amazon’s network. The best way to recognize our monitoring requests is user agent HTTP header: All our monitoring requests have the following header “User-Agent: Spatineo Monitor GetMapBot (http://www.spatineo.com/spatineo-monitor)”. Occasionally we also request the service metadata (capabilities documents) using “User-Agent: Spatineo Monitor Controller (http://www.spatineo.com/spatineo-monitor/)”.
 

How is the downtime calculated? Does one failed request constitute a downtime or are more than one failed request needed?

We send the monitoring requests for one service once every 5 minutes. The service downtime shown in Spatineo Directory is calculated based on all the requests that we have not received a standards-compliant response before the timeout (60 s). The traffic light status indicator on the Spatineo Directory pages always reflects the status of the last monitoring request.

The reported downtime period is generally estimated to have begun at the time when we get the first failed request, and ended when we manage to make the first successful request after one or more failed ones. For really short brakes the downtime is estimated to have started 2.5 minutes before the first consecutive failed request and to have ended 2.5 minutes after the last failed one. This simple way of calculating the downtime may not always give the most realistic estimate of the reliability of the services because single HTTP requests may fail for a number of reasons. However, we feel it’s not fair for the data users to ignore even short breaks in availability if they happen often. We are continuously thinking the ways to implement the most fair downtime estimations, feel free to send us any suggestions on how you feel it should be done.
 

How do I contact Spatineo?

For technical issues please feel free to email us at support (at) spatineo.com. For everything else you can reach us at info (at) spatineo.com. Or you can also call us. Check the contact page for phone numbers.