overpass-turbo icon indicating copy to clipboard operation
overpass-turbo copied to clipboard

Leveraging information in /api/status to enhance HTTP 429 error popup

Open mmd-osm opened this issue 8 years ago • 7 comments

In case there's too much load on the server or a user has exceeded the available quota, a new error message now points to the /api/status endpoint. (http://overpass-api.de/api/status):

quota

I would assume that some users might find it a bit challenging to deal with this error message, given the only relevant information being the minimum wait time before trying again.

Looking further at /api/status, the following details will be shown:

Connected as: 4352345243
Rate limit: 1
Slot available after: 2016-09-30T17:43:32Z
Currently running queries (pid, space limit, time limit, start time):

Is this something overpass turbo could help with, e.g. by enhancing the error pop up with an additional "minimum wait time: xyz minutes" explanation, taking the /api/status details into account?

It's basically the minimum date value of all Slot available after lines, in case there's no line containing slots available now exists.

Thinking about this issue a bit more, it would be even easier for data consumers to have the minimum wait time information right in the error message itself. @drolbr

mmd-osm avatar Sep 29 '16 20:09 mmd-osm

Hi I've come a cropper to this since it was introduced. I'm not saying it isn't required, but could it's limit be reviewed regularly to ensure the messages are display only when absolutely necessary. Any servers for OT should be used to their full potential.

Could either the full path to http://overpass-api.de/api/status be placed in the error window or better still just display the message as in the above post?

Could you clarify what Currently running queries (pid, space limit, time limit, start time)' means?

DaveF63 avatar Sep 30 '16 17:09 DaveF63

I'm not saying it isn't required, but could it's limit be reviewed regularly to ensure the messages are display only when absolutely necessary. Any servers for OT should be used to their full potential.

Those messages are coming directly from Overpass API server and reflect the current load on the server as well as your own quota usage.

Could you clarify what Currently running queries (pid, space limit, time limit, start time)' means?

This is probably only interesting to track down some issues. It basically lists all of your queries currently running on the server and their respective allowed/anticipated maximum time and memory usage.

mmd-osm avatar Oct 01 '16 10:10 mmd-osm

Those messages are coming directly from Overpass API server and reflect the current load on the server as well as your own quota usage.

I assume it's OT message box? To avoid confusion & further discussions like this, could it be explained with a message in the dialog?

This is probably only interesting to track down some issues.

In that case, is there any point in showing it?

DaveF63 avatar Oct 01 '16 11:10 DaveF63

could it be explained with a message in the dialog?

Yes, exactly, that's what this issue is about: adding something like "You need to wait at least xyz minutes before running the next query" to the error popup, rather than having a user figure out what to do with the link to the "/api/status" page.

In that case, is there any point in showing it?

Not really. They're helpful to calculate the wait time. For most users though, this level of detail will be irrelevant.

mmd-osm avatar Oct 01 '16 11:10 mmd-osm

Yes, exactly, that's what this issue is about: adding something like "You need to wait at least xyz minutes before running the next query"

That would a much more helpful display. Please remember that most users of OT are not experienced coders but just end users who want to click on the button 'Load' & for the program to run. Simple error messages are essential. If there's an internal Error number, display that also & ask the users to copy paste it into a bug report here. It will help both parties.

DaveF63 avatar Nov 10 '16 19:11 DaveF63

I closed this one on purpose, follow up is in https://github.com/drolbr/Overpass-API/issues/351

mmd-osm avatar Feb 08 '18 08:02 mmd-osm

I closed this one on purpose, follow up is in drolbr/Overpass-API#351

but it's still open?

axd1967 avatar Sep 09 '19 11:09 axd1967