Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

http: adjust log level for request failure #7785

Merged
merged 1 commit into from
Apr 22, 2020
Merged

Conversation

notnoop
Copy link
Contributor

@notnoop notnoop commented Apr 22, 2020

Failed requests due to API client errors are to be marked as DEBUG.

The Error log level should be reserved to signal problems with the
cluster and are actionable for nomad system operators. Logs due to
misbehaving API clients don't represent a system level problem and seem
spurious to nomad maintainers at best. These log messages can also be
attack vectors for denial of service attacks by filling servers disk
space with spurious log messages.

Fixes #7783

Failed requests due to API client errors are to be marked as DEBUG.

The Error log level should be reserved to signal problems with the
cluster and are actionable for nomad system operators.  Logs due to
misbehaving API clients don't represent a system level problem and seem
spurius to nomad maintainers at best.  These log messages can also be
attack vectors for deniel of service attacks by filling servers disk
space with spurious log messages.
@notnoop notnoop requested a review from drewbailey April 22, 2020 20:37
@notnoop notnoop self-assigned this Apr 22, 2020
Copy link
Contributor

@drewbailey drewbailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@notnoop notnoop merged commit 5973285 into master Apr 22, 2020
@notnoop notnoop deleted the b-http-fail-log-level branch April 22, 2020 21:03
notnoop pushed a commit that referenced this pull request Jul 23, 2020
@github-actions
Copy link

github-actions bot commented Jan 9, 2023

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 9, 2023
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clients querying not found endpoints aren't errors
2 participants