Suppress Azure SDK error logs#139729
Merged
DaveCTurner merged 5 commits intoelastic:mainfrom Dec 18, 2025
Merged
Conversation
It turns out that the Azure SDK logs copiously at `ERROR` level for totally benign events such as a `BlobNotFound` response when trying to delete a blob that has already been deleted. Until elastic#139226 these messages were screamed into the void and caused no issue, but since that change landed we now see them in the server logs too. In due course we'd like to be able to capture these logs at a more appropriate level, maybe `DEBUG`, but in the meantime this commit removes the SLF4J bridge from the `repository-azure` module to redirect them back into the void.
DaveCTurner
added
>non-issue
:Distributed/Snapshot/Restore
elasticsearchmachine
added
the
Team:Distributed Coordination (obsolete)
Collaborator
|
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
Collaborator
|
Hi @DaveCTurner, I've created a changelog YAML for you. |
Contributor
Author
|
This is going to land in a patch branch via #139730 but also needs backporting to 9.3 so I'm leaving this open as a reminder to do that. |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Dec 18, 2025
It turns out that the Azure SDK logs copiously at `ERROR` level for totally benign events such as a `BlobNotFound` response when trying to delete a blob that has already been deleted. Until elastic#139226 these messages were screamed into the void and caused no issue, but since that change landed we now see them in the server logs too. In due course we'd like to be able to capture these logs at a more appropriate level, maybe `DEBUG`, but in the meantime this commit removes the SLF4J bridge from the `repository-azure` module to redirect them back into the void.
Collaborator
💚 Backport successful
|
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 18, 2025
It turns out that the Azure SDK logs copiously at `ERROR` level for totally benign events such as a `BlobNotFound` response when trying to delete a blob that has already been deleted. Until #139226 these messages were screamed into the void and caused no issue, but since that change landed we now see them in the server logs too. In due course we'd like to be able to capture these logs at a more appropriate level, maybe `DEBUG`, but in the meantime this commit removes the SLF4J bridge from the `repository-azure` module to redirect them back into the void.
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
3 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.
It turns out that the Azure SDK logs copiously at
ERRORlevel fortotally benign events such as a
BlobNotFoundresponse when trying todelete a blob that has already been deleted. Until #139226 these
messages were screamed into the void and caused no issue, but since that
change landed we now see them in the server logs too.
In due course we'd like to be able to capture these logs at a more
appropriate level, maybe
DEBUG, but in the meantime this commitremoves the SLF4J bridge from the
repository-azuremodule to redirectthem back into the void.