-
Notifications
You must be signed in to change notification settings - Fork 569
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
refactor(elasticsearch-exporter): output raw message on JSON error #10971
Conversation
Ensures that the raw message is printed as part of the stacktrace when the server returns a successful, but invalid message, so we can more easily diagnose what is happening.
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.
I guess I'm a bit rusty in the HTTP client API, but I got it now after a while :D Thanks 👍
...ters/elasticsearch-exporter/src/main/java/io/camunda/zeebe/exporter/ElasticsearchClient.java
Outdated
Show resolved
Hide resolved
Your comment made me realize I should make it more explicit why we're doing this. Someone who's unaware of this error reporting behavior but aware that Jackson can deserialize an |
bors merge |
10971: refactor(elasticsearch-exporter): output raw message on JSON error r=npepinpe a=npepinpe ## Description Ensures that the raw message is printed as part of the stacktrace when the server returns a successful, but invalid message, so we can more easily diagnose what is happening. ## Related issues closes #10970 Co-authored-by: Nicolas Pepin-Perreault <nicolas.pepin-perreault@camunda.com>
Build failed: |
bors r+ |
Build succeeded: |
Successfully created backport PR #10981 for |
Description
Ensures that the raw message is printed as part of the stacktrace when the server returns a successful, but invalid message, so we can more easily diagnose what is happening.
Related issues
closes #10970
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
backport stable/1.3
) to the PR, in case that fails you need to create backports manually.Testing:
Documentation:
Please refer to our review guidelines.