@jampukka thanks, more upcoming like #285. Guess your service is the "NLS-FI topographical database - OGC WFS3", one of the few that also validates against the OpenAPI spec!
My draft pull request for the conversion to python3 (#280) is about done! :) I updated the documentation assuming the conversion to python3 will trigger a new release (v0.8.0). Feedback and suggestions are welcome!
Would you prefer a new pull request with all the commits squared into one?
@borrob Good news! See you also included recent commits. We only first need to bring out 0.7.0 before any merge. Yes, the merge button allows reviewers to squash, so no need. We'll have to review 37 files changed, try out locally, both with SQLite and PG, including with Docker. Once merged we need to go loose on the demo site, also watching logs, since it has a rich mix kinds of Resources/Probes/Checks.
Testing https://github.com/borrob/GeoHealthCheck/tree/py3, adding findings to geopython/GeoHealthCheck#280 as comments.
Think this is a good idea: "Ability to add same Service using same URL multiple times". See issue #292. Several use-cases, e.g. different schedules (once a day heavy/conformance test, every 5 mins uptime test). Change is minimal: remove check at app.py#551. I see no problems in this.
url is not a unique column in DB. If no objections I'll make the PR.
@/all 3 PRs went in yesterday, running on demo: 1) #292 can add
Resource with same URL multiple times. 2) For #296 WFS3 (OAPIF) Probe OpenAPI link convention fix and 3) PR #300 results in better root error cause Check reporting for Probes. Smallish stuff, our big chunk ahead is the Py2->Py3 migration WIP #280 led by @borrob, we're quite far, nasty details with char/bytes encodings, any help/testing appreciated!
@Erkan70 you can monitor any URL/API for availability and general health by using the
Resource Type Web Address (URL) under Add in menu. You can then configure Checks like HTTP Status and keywords in content like feed and title. To really validate Atom contents like checking its links, a specific Atom Resource Type and Atom Probes/Checks (plugins) need to be developed.
Solved it by adding a new one and deleting the old one, so maybe not worth the effort unless an easy fix
@fchtngr not the OWS responses themselves (could be 100s), but in the UI you can hover over the Run Graph (History) and then get the Full Report. There you can see which
Probes failed, and for each Probewhich Check(s). See also the Failure Analysis documentation. Also in the Edit screen you have a Test button with a similar Run report. The reporting could be improved, yes and there are cases where one would like to see the actual response, requires some thinking as Probes are executed within the server.
btw, really liking the tool so far :)
theoretically i could write a plugin that queries some features (of which some attributes are links to images/video), and check whether they all return http 200 OK. should be possible, right?
Yes, see docs. Using a "free-form"
Probe like the WMSDrilldown, anything goes as long as it returns a Result object. For OWS client calls you can use OWSLib (or just requests package).
A good one: built-in
unittest is used, run from rootdir: python tests/run_tests.py (see also .travis.yml). Beware that your instance/config_site.py is taken and that the entire DB is filled/cleaned (see #188). Room for improvement, but you can test your Plugin by extending the DB data in fixtures. This will run your Plugin automatically via run_resources.py (run_plugins.py is used to test Plugin mechanism only).
ok will need some text for: https://github.com/geopython/GeoHealthCheck/releases/tag/0.7.0 and a new Docker Image.
shall I do the Docker Image 0.7.0? Release text: Most importantly: no DB-upgrades from 0.6.0 are required. Highlights in the 0.7.0 Milestone 40 PRs and issues.
@tomkralidis see my review at #280. We're good to go! After merge in about 15 mins we can check on https://demo.geohealthcheck.org.
(crossing msgs :-))
(as Docker image is built on GH push and pulled on demo site)
(and crossing fingers)
.. build ok now.