-
Notifications
You must be signed in to change notification settings - Fork 277
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
Add more observability around WS handshake failures #6771
Add more observability around WS handshake failures #6771
Conversation
@john-markham: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/ |
✅ Docs preview has no changesThe preview was not built because there were no changes. Build ID: 0affb52a2746780446dba6f8 |
tracing::warn!( | ||
error.type = "websocket_connection_failed", | ||
error.details= %error_details, | ||
error.source = %std::any::type_name_of_val(&err), | ||
"WebSocket connection failed" | ||
); |
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.
It looks good but I don't think this part is needed as we're returning the SubrequestWsError
we should be able to display it using custom telemetry configuration. Also might be worth to add the source
to SubrequestWsError
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.
We can leave adding additional metadata to SubrequestWsError
to a followup
c02b6d3
to
c498ae6
Compare
c498ae6
to
9d45f12
Compare
35e3083
to
b62176f
Compare
2de21a1
to
c561dd4
Compare
8be1b17
to
7fd6e95
Compare
9f9f20f
to
22a7368
Compare
22a7368
to
d8c40ab
Compare
Signed-off-by: Benjamin <5719034+bnjjj@users.noreply.github.com>
Thanks @john-markham closing this PR in favor of #6798 |
Description here
Fixes #issue_number
Checklist
Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.
Exceptions
Note any exceptions here
Notes
Footnotes
It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩
Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩
Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩