Fix Cloudwatch remote logging crash API server if ResourceNotFoundException#68781
Open
jason810496 wants to merge 1 commit into
Open
Conversation
boring-cyborg
Bot
added
area:logging
area:providers
provider:amazon
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
1 participant
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.
Why
While trying to setup cloudwatch remote logging in #68709 in order to persist the logs in real time. I caught another error that if API server encounter
ResourceNotFoundExceptionerror from cloudwatch remote logging setup, it will raise internal error with500status code instead of showing verbose hints for user on Airflow UI.What
Capture the exception and return user-facing error message as
CloudWatchLogEventcompatible format so that it could show on the Airflow UI properly.Verification