-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Query metrics #232
Comments
A user notified us that the AAT wasn't available on 13-10-2022 (morning), 7-12-2022 (1,5 hour) and 7-12-2022 (13:30-15:15). The user, wanting to reconcile terms on location at heritage organisations, switched to the Getty reconciliation API of the AAT (English). We should be able to measure the availability of sources in order to start the conversation with the maintainer of the (SPARQL endpoint) of a termsource, or to decide to decommission a termsource, as the performance and availability of sources reflects on the Network of Terms! |
So was this due to the Network of Terms itself or the AAT not being available? See also #766. |
In this case the AAT. But in general when the source is down/not performant, this reflects on the Network of Terms. |
We now return response times per source (#856). |
And we keep statistics (behind login) at https://statistieken.netwerkdigitaalerfgoed.nl, so closing this. |
Monitor and (publicly) graph the amount of queries executed per term source. We could use Prometheus.
The text was updated successfully, but these errors were encountered: