Quieten many ERROR logs to WARN#139799
Merged
DaveCTurner merged 3 commits intoelastic:mainfrom Dec 19, 2025
Merged
Conversation
Today we're egregiously over-using the `ERROR` log level to report situations that do occur sometimes but which can safely be ignored. At least, we are in practice already ignoring these things despite the overly-dramatic logging. In order to move to a model where we can rely on elevated `ERROR` logging as an indicator of a truly release-stopping bugs, this commit reduces a number of the worst offenders down to level `WARN`.
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Member
Author
|
I know it's not really |
jimczi
approved these changes
Dec 19, 2025
szybia
added a commit
to szybia/elasticsearch
that referenced
this pull request
Dec 19, 2025
* upstream/main: Update text_similarity_rank_retriever to support inference ID as an argument when reranking on chunks (elastic#137397) Mute org.elasticsearch.test.rest.yaml.CssSearchYamlTestSuiteIT test {p0=search.retrievers/result-diversification/10_mmr_result_diversification_retriever/Test MMR result diversification multiple indexes} elastic#139826 Mute org.elasticsearch.index.mapper.SkipperSettingsTests testTSDBSkipperSettingDefaults elastic#139824 Unmute test fix elastic#129517 (elastic#139782) Add back support for deserializing old refresh token in test (elastic#139811) Add documentation for exponential_histogram field type (elastic#139684) make ES|QL sample CSV test looser (elastic#139814) Add `frozen_after` field to data stream lifecycle (elastic#139042) Quieten many `ERROR` logs to `WARN` (elastic#139799)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Today we're egregiously over-using the
ERRORlog level to reportsituations that do occur sometimes but which can safely be ignored. At
least, we are in practice already ignoring these things despite the
overly-dramatic logging. In order to move to a model where we can rely
on elevated
ERRORlogging as an indicator of a truly release-stoppingbug, this commit reduces a number of the worst offenders down to level
WARN.