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

Don't report 504 as error to New Relic #51

Merged
merged 3 commits into from
Nov 12, 2015
Merged

Don't report 504 as error to New Relic #51

merged 3 commits into from
Nov 12, 2015

Conversation

bergie
Copy link
Member

@bergie bergie commented Nov 11, 2015

504 is essentially ImgFlo's 404, so it shouldn't be sent to New Relic as an error in order to prevent false alarms.

504 is essentially ImgFlo's 404, so it shouldn't be sent to New Relic as an error in order to prevent false alarms.
@jonnor
Copy link
Member

jonnor commented Nov 11, 2015

@bergie Should we just change this to be a 404 instead of special casing it?

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

Successfully merging this pull request may close these issues.

2 participants