-
Notifications
You must be signed in to change notification settings - Fork 5k
[AWS Health] Improve error message reporting #45408
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
[AWS Health] Improve error message reporting #45408
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
@agithomas Do we need any backport labels here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@Mergifyio backport 8.17 8.18 8.19 9.0 9.1 |
✅ Backports have been created
|
* parse error message * remove comment * fix CI * add changelog entry (cherry picked from commit 1637c55) # Conflicts: # x-pack/metricbeat/module/aws/awshealth/awshealth.go
* parse error message * remove comment * fix CI * add changelog entry (cherry picked from commit 1637c55) # Conflicts: # x-pack/metricbeat/module/aws/awshealth/awshealth.go
* parse error message * remove comment * fix CI * add changelog entry (cherry picked from commit 1637c55)
* parse error message * remove comment * fix CI * add changelog entry (cherry picked from commit 1637c55)
* parse error message * remove comment * fix CI * add changelog entry (cherry picked from commit 1637c55) # Conflicts: # x-pack/metricbeat/module/aws/awshealth/awshealth.go
Proposed commit message
Make error messages explicit by parsing them using smithy library.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs