Skip to content
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

Change S3 access error level to debug #7620

Open
txau opened this issue Jan 29, 2025 · 0 comments
Open

Change S3 access error level to debug #7620

txau opened this issue Jan 29, 2025 · 0 comments

Comments

@txau
Copy link
Collaborator

txau commented Jan 29, 2025

Every now and then there are small intermittences in the S3 service, resulting in requests responding with a 500 and flooding our logs with critical notifications.

If we can assume eventual failure of S3, we don't need to record these logs as critical.

  1. Change the level of the log from error to debug
  2. Change the response code from 500 to 503
The 503 Service Unavailable response code means that the server is currently not ready to handle the request. This is a common occurrence when the server is down for maintenance or is overloaded.

When looking at things SEO-wise the 503 Service Unavailable status code means that the server is unavailable and the visitor, bot or human, is asked to return again at a later time. This could be because of either server maintenance or server overload and search engines know to come back and check the availability later.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant