You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The email alerts we send out at present do an okay job of letting a scraper owner know that their individual scraper is failing (and #1213 has suggestions for making that even better)
'
But morph as a platform has had some systemic issues that broke most SSL connections (#1196, #1201) or all PHP scrapers (#1204). At present we don't have any overall statistics that let us find these problems.
If we could log, at the end of each scraper run, details such as its language and language version, as well as the first line of the error message (if the scraper errored), I think this would help us to be able to spot things like "90% of PHP scrapers are failing" or "80% of scraper failures seem to be SSL errors".
The text was updated successfully, but these errors were encountered:
Inspired by #1213 and #1204 and #1201 and #1196
The email alerts we send out at present do an okay job of letting a scraper owner know that their individual scraper is failing (and #1213 has suggestions for making that even better)
'
But morph as a platform has had some systemic issues that broke most SSL connections (#1196, #1201) or all PHP scrapers (#1204). At present we don't have any overall statistics that let us find these problems.
If we could log, at the end of each scraper run, details such as its language and language version, as well as the first line of the error message (if the scraper errored), I think this would help us to be able to spot things like "90% of PHP scrapers are failing" or "80% of scraper failures seem to be SSL errors".
The text was updated successfully, but these errors were encountered: