GeoHealthCheck icon indicating copy to clipboard operation
GeoHealthCheck copied to clipboard

Service Status and QoS Checker for OGC Web Services

Results 92 GeoHealthCheck issues
Sort by recently updated
recently updated
newest added

I have a GHC instance running locally on port 8083 (see the Docker example). So GHC can be accessed by navigating in the browser to http://localhost:8083. I have tested the...

bug

The script to create a new database prints the admin password to the console. This is undesirable for security purposes. Often console output (of Docker containers or otherwise) is accumulated...

bug

**Describe the bug** The probes GetMap, GetFeatures and GetTiles sometimes give false errors when there are many resources (1000) running with a short run_frequency (i.e. 5 minutes). **To Reproduce** Steps...

bug

**Is your feature request related to a problem? Please describe.** - To schedule new jobs for a new quality control, you might want to time it in such a way...

enhancement

**Is your feature request related to a problem? Please describe.** For OAFeat generic Probes exist but more fine-grained health-checking is needed. **Describe the solution you'd like** An `OGCAPIFeaturesCollection` `Probe` would...

enhancement

**Is your feature request related to a problem? Please describe.** Several cases where access to GHC data is required in custom monitoring and reporting tools. Though a full CRUD API...

enhancement

**Is your feature request related to a problem? Please describe.** When configuring a WMS/WFS getMap/getFeature probe, GHC shows a dropdown with the available layers. If you want to monitor 'hidden'...

enhancement

**Is your feature request related to a problem? Please describe.** For some resources you'll want to configure multiple probes of the same type with their own checks. If one of...

enhancement

On an individual resource page, a user cannot see the `GHC_NOTIFICATIONS_EMAILS` that a notification will be sent to. ### Solution On resource creation, only the current logged in users email...

enhancement

As follow up on issue #189 and discussion in PR #310: The current CLI commands are: `build-wheel` `clean` `create-hash` `create-instance` `create-secret-key` `create-wsgi` `db` `lang-add-language-catalogue` `lang-compile-translations` `lang-extract-translations` `lang-update-translations` `run-healthchecks` `run-tests` `runner-daemon`...

enhancement